Do you have questions about the Windows®
Server 2003 operating system for our Windows-based hosting plans? Well, here's
were you'll find answers to some of the more common questions that are asked
about our Windows Server 2003.
______________________________________________
Q: Can I migrate the Windows 2003 Server plans into the Windows Server 2000 plans?
A: The Plan Change Tool does not support this type of migration. Do not attempt to process this change as it will result in downtime and technical problems to the site. If you have any questions or concerns, contact RapidSite Support.
Q: Will Verio Inc. stop selling the Windows Server 2000 plans?
A: Verio Inc. has plans to stop selling majority of the Windows Server 2000 plans on February 9, 2004. The Windows Server 2000 Ecommerce plan {Win2k EC} and the Windows Managed Server (WMS) will remain active, but the others will not be orderable after February 9, 2004. All existing Windows Server 2000 plans will remain active unless the account changed plan types or cancelled.
Q: Does Verio have plans to migrate its Windows Server 2000 plans into Windows Server 2003 plans?
A: No. However, if such a migration plan later becomes a possibility, we will send an announcement to all of our Partners and we will also post that announcement prominently in the Dealer Kit.
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 has improvements
and additions for application services, security, and much more. Most of these
improvements will be transparent to you as they apply to 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: Can I migrate
any of the Windows 2000 Server plans into the Windows Server 2003 plans?
A: The Plan Change Tool within the customer Control Panel supports a plan change from a Windows 2000 Server plan into the selected Windows Server 2003 plan. The migration process involves a Server Move. Details regarding server moves can be found on the Dealer Kit. Additionally, you can contact our Technical Support team for assistance.
Q: When will I be
able to migrate a UNIX or FreeBSD plan over to the Windows Server 2003 plans?
A: As of January 2004, The Plan Change Tool supports UNIX or FreeBSD plans migrating into the Windows Server 2003 plans. The migration process involves a Server Move. Details regarding server moves can be found on the Dealer Kit. Additionally, you can contact our Technical Support team for assistance.
Q: Do I need to
make any changes in my web site's code or applications?
A: If you choose 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.
Q: What functional
issues should I know with regard your 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 Server
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 Server, ActivePerl version 5.6 is installed on Windows
Server 2003.
CDO (Collaboration Data Objects) 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
neither delete this directory nor 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. Additionally, ODBC.NET data provider and ASP.NET Mobile
Controls are now integrated into Windows Server 2003.
Q: What are the hardware specifications of the new Windows 2003 server plans?
A:
- MotherBoard: Intel® Server Board SE7500WV2
- Processors: Dual Intel 1.4ghz Xeons
- Drives: 36GB and 73GB SCSI Seagate 10,000 RPM HDD
- Raid level 1 and 1+0 arays, Mylex 170 RAID cards
- Memory: 2GB PC2100 DDR RAM
- Backups: Rapidsite Backup v2.2 or Legato Networker backups
- Hardware: Spectra Logic 10,000 AIT2 50GB tapes
Q: Where can I go
for further information regarding Windows Server 2003?
A: Please visit our Where do I find
technical information about Windows Server 2003? web page for a list of
useful Windows Server 2003 resources.