Beruflich Dokumente
Kultur Dokumente
Revision History
Revision Revision Summary of Changes Changed by
Number Date (Acronym)
1.0 18/10/04 First release SRO
Corrected password for EURCTXFarmAdmin.
1.1 01/12/04 Included registry hack for the configuration of page file for servers with more SRO/HBO
than 4 GB of memory
1.2 03/06/05 Registry setting to remove /3GB switch in boot.ini file SRO
Table Of Contents
1. Introduction....................................................................... .........................3
2. Audience................................................................................ .....................3
3. Prerequisites.............................................................. ................................3
4. Procedure................................................................... ................................4
1.Introduction
As more and more SNOASIS servers are being deployed through Europe, it has been decided to
delegate the installation of the SNOASIS layer from the Technology team to the Windows 2000
Deployment team.
This document explains all the steps to follow for the installation of the SNOASIS layer on top of an
existing Oasis server.
2.Audience
The audience targeted by this document is the Windows 2000 Deployment team.
3.Prerequisites
• The server on which you want to install the SNOASIS layer must be running Oasis 2226
and must be joined to the nestle.com domain before you start the procedure.
• If the server has more than 3.5 GB of physical memory, the line for the Windows instance in
the boot.ini file should include the /PAE switch as last argument.
• You should have administrative rights on the server (typically, an adm2 account).
• You should know the location of the WTSProfiles share for the site 1.
• You should know the location of the CITRIX-2226 share for the site 2.
• The server should be created with the appropriate tasks in PDBnet, so you can track the
steps already done.
• You should have a Peregrine RM ticket.
• The server should be in maintenance mode during the installation, as several reboots are
needed.
1
See the Technology team for this piece of information.
2
See the Technology team for this piece of information.
4.Procedure
Log on to the server with your administrative account.
Include the computer account of the server into the group EUR: TS Policy.
Start the Add/Remove Programs applet from the Control Panel and click on Add/Remove Windows
Components:
Click on Components:
Click on Next:
Choose Permissions compatible with Terminal Server 4.0 Users and click on Next:
Click on Next:
Now set the WTSProfilesShare system variable by executing the following command:
Set the initial and maximum sizes for the paging file to 2 * physical memory of the server. In the
same dialog box, set the maximum registry size to 120 MB:
To create multiple paging files on one volume to overcome the 4,095-MB limit:
1. Using Registry Editor (Regedt32.exe only), locate the following key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\MemoryManagement
If the system has 6 GB of memory, create the following paging files in the registry:
Location Min Max
C:\pagefile1.sys 4092 4092
C:\pagefile2.sys 2048 2048
F:\pagefile1.sys 4092 4092
F:\pagefile2.sys 2048 2048
If the system has 8 GB of memory, create the following paging files in the registry:
Location Min Max
C:\pagefile1.sys 4092 4092
C:\pagefile2.sys 4092 4092
F:\pagefile1.sys 4092 4092
F:\pagefile2.sys 4092 4092
Note that if the C: drive is not big enough, but the F: drive has enough space, you can put all page
files on F: drive.
Best performances are achieved when each volume (C: and F:) resides on separate arrays
controlled by different RAID adapters.
Now, you must disable the /3GB switch in the boot.ini file of the server. In order to do so, open the
Registry Editor and go to the following key:
HKLM\Software\Nestle\OASIS
This will ensure that the /3GB is removed in the boot.ini file at next boot (FYI, this is preformed by
the startup script).
Open the properties of the production network adapter (or the team, if teaming software is installed
and configured), select File and Printer Sharing for Microsoft Networks and click on
Properties:
Choose Maximize data throughput for network applications and click on OK:
Click on OK to close the properties of the network adapter (or the team).
Map the W: to the CITRIX-2226 share of the site (check the Reconnect at logon box).
Once the copy is over, the script will ask you to provide several parameters. The first question is
about what you want to do. In your case, select option 2 in the following menu:
As we are running the SQL datastore on SQL server, select (SQL Server):
This will start the unattended installation of MetaFrame. Wait while the software is being installed
on the server:
When you get the following window, the installation of MetaFrame is over. Press Enter and the
server will reboot by itself:
After the reboot, log on to the server. Press Enter twice in the following window to start the post-
install script:
This window will close by itself once the script has run.
When the installation is finished, you will get the following window:
Start the WTS script again (type wts in the DOS box) and select option 7 (Install GoldPlus
Applications).
Again, this will take some time to complete:
When the installation is finished, you will get the following window:
The last software to install are the TS tools for Office 2000. Here is how to proceed: in the DOS
box, enter the follow commands:
The system will confirm that the registry file has been correctly imported. Press OK to close the
window:
Enter the following command in the DOS box (this command makes sure that the changes
performed in the registry will be active for all users):
3
Replace DEMDCW00 by the name of the server hosting the Citrix 2226 share.
Go back to the DOS box and enter the command change user /execute (this will re-enable
registry shadowing):
Reboot the server and assign the Peregrine RM ticket to the EUR_W2K Technical resolution
group.