Application deplo ment with Windows 2003 Server - www.alanphipps.com
Ads b Google Spam Ser er DC Windo s Ghost Windo s Ser er 2003
Applica ion Deplo men - Se
e Deplo men
Software Design Tool
Create software UI protot pes fast. GUI design tool. 30-da Free Trial.
Commodit Trade Software
Manage End to End Ph sical TradingTraffic,Risk,Finance, M2M, Contract
The main deployment technique was initiated by logon script and used Microsoft's Elevated Privileges Application Launcher (EPAL) to install the Outlook package with local admin rights while the user was logged on with their normal non-admin credentials. The server deployment process is explained below: Step 1 - Create the Outlook Package Step 2 - ReplicateOutlook Package and Configure EPAL Step 3 - Create and Configure the Active Directory Users and Groups Step 4 - Write the scripts that install the application Step 5 - Last Minute Checks Step 6 - Troubleshooting
Top 10 HR Software
Get Free HR Evaluation Reports for Software Selections & Comparisons!
S ep 1 - C ea e he O lookPackage
Using the files from the MS Office CD you must first create the Installation package to be used for the CD. Obviously not all the Office files are necessary, a complete list of all files necessary to install outlook can be found here. Once all files have been copied to a separate folder you can then create the Outlook Transforms file that will automatically configure the installation,this can be done as shown here. Lastly, you must create a PRF file that will configure such settings as the default Exchange server and Cached Exchange Mode, again this can be done as shown here. Please note that this process uses an pre-configured email address to receive the results of the install, this mailbox should be ready for use before the scripts are made active. Once the mailboxes are readyyou should put the email addresses in the scripts. All computers will require an internet connection to use the email address.
S ep 2 - Replica e O
look Package and Config
The Outlook package was stored on a Domain Controller's Netlogon share in a folder named Netlogon\Deploy\yellowOutlook. When placing files in the netlogon folder, the files will be automatically copied to thesame folder on all domain controllers for that domain. Remember that if you copy the same files to multiple DC's at the same time, windows will see them as different files and make separate copies of each file, on each DC, meaning that if you copy the outlook package onto 3 DCs then once replication is complete there will be 3 separate folders with different names on each DC. Copy the outlookpackage to 1 DC and let windows do the rest, if you have a large network then it might be a good idea to start the copy at the weekend. Also copy Sleep.exe to the Netlogon folder, Sleep.exe is part of the Window 2003 Resource Kit. Config ing EPAL
Configuring EPAL can be quite difficult, so I will try to explain it as best I can. A separate EPAL configuration must be made for each DomainController, where the EPAL config will have a unique name. The EPAL configuration process is as follows: Create the DC specific EPAL Program Files Register the EPAL program with Active Directory
C ea e he DC Specific EPAL P og am File I used the first 4 letters of the Domain Controller's location to name the EPAL program Files, which in my case was how the DCs were named anyway, so it was easy to seewhat files were linked with which EPAL program. The Outlook package had been replicated to each DC's netlogon share to the path \\Servername\Netlogon\Deploy\YellowOutlook, inside this folder you should create another folder called EPAL and copy the EPAL executable to the this folder. Now make a copy of the Outlook Setup executable SETUPOLK.exe, 1 for each DC. Rename the new executables with the DC...