Linux םירתא ןוסחיא
Starter םירתא ןוסחא
Mini רתא ןוסחא
Regular םירתא ןוסחיא
Midi רתא ןוסחיא
Extra םירתא ןוסחא
(ילאוטריו) המצוע רתא ןוסחיא
תונולחב םירתא ןוסחיא
Mini םירתא חוריא
Regular רתא חוריא
Midi םירתא חוריא
Extra רתא חוריא
םיילאוטריו םיתרש ןוסחיא
הפוריאב םירתא חוריא
SSL הנפצה תוחתפמ
לארשי םירתא ןוסכיא
לארשי םיתרש חורא
ןיימוד
|
Windows Server 2003 Migration FAQ
Here you'll
find answers to some of the more general questions about migrating to Windows
Server 2003. This FAQ provides a good overall understanding of what is involved
with such a migration. For in-depth information regarding the more technical
aspects of migrating to Windows Server 2003, we suggest that you read our Windows Server 2003 Migration
Checklist. That checklist is located in the "Windows Hosting Specific"
section of the Technical Support area of the RapidSite Dealer Kit.
______________________________________________________________
Contents
Q: What type of migration is being offered?
A: We are offering our customers the option to migrate from Windows 2000
Server to Windows Server 2003. Migration is not mandatory. You can choose to
stay with Windows 2000 Server if you wish. However, migrating to Windows Server
2003 has definite advantages over staying with Windows 2000 Server. For details,
please read this FAQ in its entirety.
Q: Why is RapidSite
offering this migration?
A: This migration is being offered as a beneficial technology upgrade.
Windows Server 2003 tightly integrates a number of functions that, in Windows
2000 Server, were add-ons. For example, .NET Framework is now integrated into
Windows Server 2003.
Additionally, Windows Server 2003 is Microsoft's latest server offering,
incorporating significantly enhanced performance, reliability and security.
Built from "the ground up" to incorporate ASP.NET, this web hosting
platform has all the same customer features of our Windows 2000 Server platform
(except for ASPmail support) while providing a flexible platform for the future.
Q: If I choose
to migrate, what would it cost me?
A: It would cost you zero dollars: There is no price change or set up
fee involved with the migration. The migration to Windows Server 2003 is completely
free.
Q: When can I
migrate from a Windows Server 2000 plan to a Windows Server 2003 plan?
A:
Migration capability is now active. So, you can migrate (move to a same level plan) your Windows Server 2000 accounts at your convenience. Alternately, you can also upgrade to a different level Windows Server 2003 plan. As the migration process involves a server move,
we suggest that you read our Windows Server 2003 Migration
Checklist to make any necessary preparations prior to the migration.
Q: Can
I migrate from a FreeBSD plan to a Windows Server 2003
plan?
A: Yes. You can migrate web hosting accounts from any FreeBSD hosting plan to any Windows Server 2003 hosting plan.
Q: Do I need
to make any changes in my web site's code or applications?
A: If you choose to migrate to Windows Server 2003, the following two
areas may require your attention:
- .NET Framework:
Windows Server 2003 has .NET Framework 1.1 integrated within it. We recommend
that you use .NET Framework 1.1 to compile applications for Windows Server
2003. If, instead, you choose to use .NET Framework 1.0, you may want to keep
tabs on applications created within it so as to make sure that they run properly
under version 1.1. In the great majority of cases, you should encounter
no problems. However, if you do discover an incompatibility or glitch, please
contact our Technical Support team.
- ASPmail-to-CDOmail:
Our Windows Server 2003 plans will not support ASPmail. If you choose Windows
Server 2003, you should use CDO mail or the native .NET mail solution. Note that
we will continue to support ASPmail on our Windows 2000 Server plans.
In addition
to the two above-mentioned areas, there are some additional areas that may also
require your attention. To get an full understanding of some of the technical
issues that you should check before migrating, we suggest that you read our
Windows Server 2003 Migration
Checklist prior to migrating to Windows Server 2003.
Q: What functional issues
should I know with regard to the implementation of Windows Server 2003?
A: The functional issues that you should know include the following:
- The version of Windows
Server 2003 that we are making available to you is the Standard Edition, not
the Enterprise, Datacenter or Web edition.
- Plan changes are currently
unavailable. If you choose a Windows Server 2003 offering, you must set up
a new account.
- Regarding
databases, SQL setup is the same as it was on our Windows 2000 plans, single
SQL server.
- The server naming convention
for our Windows Server 2003 servers is "w3wXXXXX". The first two
"X's" following "w3w" are the server group number
and the final three "X's" are the server number.
- As with Windows 2000,
ActivePerl version 8.07 is installed on Windows Server 2003.
- CDO (Collaboration
Data Object) is installed on Windows Server 2003.
- Microsoft SharePoint
technology is not currently supported.
- The "stats"
directory is now a virtual directory. As such, you cannot delete this directory
or upload data to it.
Q: How would I
benefit by choosing to go with Windows Server 2003?
A: Windows
Server 2003 contains all of the functionality of Windows 2000 Server and more.
For instance, Windows 2000 Server supports .NET Framework as does Windows Server
2003: the only difference is that on Windows Server 2003, .NET Framework is
built-in. Other functions that are now integrated into Windows Server 2003 are:
- ODBC.NET data provider
- ASP.NET Mobile Controls
Q: Are your Windows
Server 2003 plans covered by the 99.9% uptime guarantee?
A: Yes.
Q: What new features
are in Windows Server 2003?
A: Windows Server 2003 contains numerous new features and abilities that make
it a more robust and flexible web hosting system. Windows Server
2003 contains improvements and additions for application services, security,
and much more. Most of these improvements will be transparent to you as they
apply to the our server-side of your hosting plan. In
addition, you can now install components that fit the ASP.NET installation model
that our servers allow.
For example, you can upload .NET assemblies (a form of Dynamic Link Library
or DLL). To upload an assembly, just copy it to the /bin directory of the relevant
IIS application. Visual Studio
.NET offers the easiest method of uploading .NET assemblies as it uploads
them automatically when you deploy your Visual Studio.NET project to the server.
Additionally, .NET assemblies can also be uploaded through an FTP client or
through Microsoft® FrontPage.
Q: Should I be
worried that Windows Server 2003 doesn't support ASPmail?
A: No. Windows Server 2003 contains a robust and flexible alternative
to sending mail from ASP pages. Specifically, you can easily replace ASPmail
functionality with CDO. CDO is built into Windows Server 2003. The transition
from ASPmail to CDO is straightforward. For more information, read our
Windows Server 2003 Migration
Checklist.
Q: Where
can I go for further information regarding
Windows Server 2003?
A: Please visit our "Windows Server 2003: Technical Information"
document for a list of useful Windows Server 2003 resources. That document
is available in the Windows Hosting Specific section of the Technical Support
area of the RapidSite Dealer Kit. Prior to migration, you should also take the
time to read our Windows Server
2003 Migration Checklist.
|