Deploying Updates to TermServer

[kjjdelist]

There has to be a better way...

Currently I am manually deploying my update packages to my W2K Terminal
Servers w/Citrix using the Add/Remove Programms feature. It's killing me
having to wait until late in the day or to come in early to apply these
packages when nobody is connected to the Terminal Servers.

Is there a tool available that will automate the Package Install on the term
server or any other way of doing this?

B7332, SP11.3, MSSQL 7.0, NT4.0 Enterprise, W2K TermServers

 

[mmcgraw]

Great question. We're wondering about the same thing. Can OneWorld Client
listener run on a Citrix Server? If it could run in Network Listener mode
this might work. Anyone using Client Listener for unattended update client
packages?

Xe sp 15.1, Coexistant OS/400 v4r5, DS MSSS 7.0, 4 Citrix Servers.

Matt

 

[Kieran_Mahony]

Hi
Try this scenario:-

Put the server into install mode (I think that is whats its called) via a
batch file. I have never tried this but it should work. You may need to
restart using the shutdown command for this to take affect.
Then run another batch file to do a silent setup (See our JDE manual for
parameters).
You should be able to schedule all this.

Cheers
Kieran




There has to be a better way...

Currently I am manually deploying my update packages to my W2K Terminal
Servers w/Citrix using the Add/Remove Programms feature. It's killing me
having to wait until late in the day or to come in early to apply these
packages when nobody is connected to the Terminal Servers.

Is there a tool available that will automate the Package Install on the
term
server or any other way of doing this?

B7332, SP11.3, MSSQL 7.0, NT4.0 Enterprise, W2K TermServers





--------------------------

 

[noj]

Another option if you have more than one server is to deploy it to one server then copy the spec files around to the other servers using a batch file.

Obviously this only works if evryone is off the servers which can be checked through the batch file, and that you are not doing service packs etc!

 

[Carl_Fisher]

I do a simple trick - copy all the new files from SPEC and BIN32 onto the
Terminal Server to a temporary environment. You can get a full set from the
Deployment Server - see Parent Package of your update package.

You can then set a simple batch job up to run out of hours which copies
these files into the Prod Environment (simple .BAT file and copy). If you
put the temporary copy on the same disk as the Prod Environment it runs
quite quickly. I have not seen the need to be in install mode for this to
work.

For the odd revised SPEC file I have even done the copy as a MOVE
interactively, it is normally quick enough not to affect users (the Spec
file is just locked briefly), this is a high risk approach, but if a report
needs deploying urgently it can work.

Otherwise if you have some built in redundancy in your TSE set-up (this is
recommended) then do it a server at a time ,

Disable New Logons, get users to Logoff and on again (this will clear the
server and move them onto another box), do the update, then Enable New
Logons and move to the next server, a bit annoying for users, but they
should only have to Log on and off a couple of times. Best done at a quiet
time when there are only a few users, eg early morning, lunchtime, or early
evening.

The only thing you have to watch is for UBE Versions, these can be created
on the TSE Client, and will be lost if you overwrite the SPEC files, just
make sure users have done a full Check In before you start. They should do
this anyway, otherwise they cannot get back to the Version when they next
log in (unless by chance they get the same TSE Server, in a large farm this
is unlikely).



OW733.3 Xe SP 14.2
Enterprise Server - Intel NT + Oracle 8.0.6
Client - Citrix TSE + 4 NT PC's for development