I require a simple VBscript for use as part of a Windows terminal services login script. It will be used for application compatibility.
Essentially, a simple script that will check for a value in the HKCU portion of the registry for a flag. This flag relates to a numbered increment. If the value is present, skip to the next part. If a lower version or absent, then either a)copy files b)write to the registry c)both
The Background:
This script will be used for application compatibility on a Citrix server. On Citrix, application execution happens on a remote server, instead of on the user’s workstation. A client app allows you to see a ‘representation’ of what is happening on the server. Each server can be running multiple user sessions of the same app.
Normally, when you run an application on your PC for the first time, the Windows installer can write any user specific settings it needs using the repair feature, in conjunction with the ActiveSetup key. This allows the application to add any files or registry entries in to the user’s profile (the profile obviously wasn’t present when the app was installed).
When the user launches the app in a Citrix’seamless window’, a reduced shell is used,and this process doesn’t happen. I want to come up with a scripted solution that allows me to add user-specific application settings.
How it would work:
The vb script would be called as part of a login script, and execute for all users. We don’t want to copy all the required registry/file entries every time a user logs on, so the script has to include some logic.
The logic would say:
1. Check to see if this user has logged on to this server type before – there will be 6 server types initially, each with a different set of applications (silo)installed.
2. If they have logged on to this servertype before, what is the version of the application set? i.e. read a value from HKCU
3. If the application set is current, skip to the end (this means the user has all the required user-specific settings for all the applications currently installed on this servertype)
4. If the application set is not current, execute a subset of commands, which will be comprised of copying files or adding registry entries.
These commands will be specific to the server type i.e. they will be settings that relate to the apps currently installed on that server.
5. When this is complete, write a value to the HKCU portion of the registry to say – Servertype version 001. This is the value that gets read in step 1.
The outcome will be that the next time a user logs on to that servertype, it wont re-run the reg/file copy actions.
If however, an administrator installs a new application on the servertype, they will add the necessary file/reg actions to the script, and increment the servertype value.
Example:
Say the servertype is named SILO-A. The admin installs a new app, and adds a REGWRITE to the script. Also, the servertype value will be incremented to SILO-A=002. When our user next logs on, the login script will check the value listed in his HKCU and find SILO-A=001, and will therefore know to go ahead and execute the updated reg/file actions for that servertype.
Script—————————-
Is HKCU SILO-A=002
yes – skip to end
no – Execute script actions under the SILO-A section
SILO-A
copy file xxx
copy file xxx
copy file xxx
regwrite xxx
regwrite xxx
regwrite xxx
update HKCU value for SILO-A to 002
SILO-B
etc
Phew! I hope that is clear
