We are preparing a rollout of Kixtart 4.x to our enterprise. We have a Change Management process in place to have changes to our servers/clients, so that we are (1)Held accountable (2)We have a backout process (3)We are under scrutiny (Auditors).

Anyway, here is the information I submitted for tomorrow's meeting. Any comments/ideas are welcome.

Description of Change:
Ongoing PCM..
This will affect the following files:
KIX32.EXE - KIXTART executable > KiX2001.402 Once 4.10 gets out of "Release Candidate" status, take the KIX32.EXE file to this new version.
KX16.DLL - DLL Needed for 9x clients
KX32.DLL - DLL Needed for 9x clients
KX95.DLL - DLL Needed for 9x clients
KXRPC.EXE - Executable needed for the Domain Controllers for Win9x compatibility, runs as a service.
NTLOGON.BAT - Common Batch file
KIXTART.KIX - Main Company Logon script
KIXTARTM.KIX - Sub-Company Logon script

This may affect the following files (Sub-Company -specific):
CITRIX.KIX - Citrix Configuration script
DEFPRTR.KIX - Default Printer Script
NOGAMES.KIX - Removes common Windows Games from the system
OLCFG.KIX - Configures Outlook

Phase 1
Initial rollout of Kixtart 4.10 (KIX32.EXE or executable) to IT Network Engineering/Network Engineering. This will be done on client login via the NTLOGON.BAT file.

Phase 2
Update NTLOGON.BAT to be "Windows XP Friendly"
Using MS "Q" Article - http://support.microsoft.com/default.aspx?scid=kb;en-us;Q318689

Phase 3
Update all clients/servers across The Enterprise to use Kixtart 4.10. This will be done on client login via the NTLOGON.BAT file.

Phase 4
Use Kixtart across all clients/servers
On servers, there are detection pieces we can use where if you login, it will leave. No need for the use of GETTYPE.EXE from the Resource kit.

Phase 5
Go through the KIXTARTM.KIX file and update groups/procedures to be up-to-date with changes that have been made in the systems.

We will want to insure that all clients are functioning properly before implementing any COM, ADSI, etc. before using it within the scripts

Impact of Change:
With Kixtart 4.x, you will gain the ability to use COM,ADSI,WMI, etc. There are also enhanced components to detect servers, etc.

Back-out Procedure:
Create copies of the scripts and revert to version 3.63 of Kixtart (currently in production). The executable KIX32.EXE can be brought back from the logon share. Alternatively, the KIX32.EXE from version 3.63 could be renamed to be KIX32.363 on the client workstation and if needed, a Support Agent could rename this file back to be KIX32.EXE locally.

Thank you,

Kent Dyer
_________________________
Utilize these resources:
UDFs (Full List)
KiXtart FAQ & How to's