1. In previous versions, you included the DLLs regardless of platform. Do you intend
   to install the DLLs only on Wintendo with the new version?
   
   Answer:
   It has impact on all kind of other tools and script of our site, which doesn't mean
   we are thinking about it. Ruud advise also not install them in a none windows9x envi-
   ronment.
   We put in on our TO-DO list.
2. In previous versions you bundled KiX32 and WKiX32 separately. Do you plan to
   change that and have both in one package?
   Answer:
   In an earlier reaction we want to keep it clear which version you are installing.
   - WKIX32 may not influence KIX32
   - for the not-experts the installation must be clear
   Questions:
   - what is the actual goal for combining them?
   - are you trying to install both versions at the same time or to install only one
   version based on specified parameter? we are also restricted by the way iexpress
   software is working.
   A possible way of passing information through installation script is by using
   environment variables like kix-debug and kix-show.
3. In previous versions you would explicitly remove associations to .SCR that could
   affect screensavers. Do you plan to leave the registry alone in the new version?
   Answer:
   it is a good point. For our environments the SCR association isn't necessary.
   All our scripts are using KIX or K2K as extension.
   
   Indeed it isn't always necessary to change or to remove file associations. We suggest
   to remove only those file associations, when they were created by the kixregistry
   version.
   Also we suggest to remove SCR association for the Kixtart 4.x releases.
   The Kixtart 3.x releases are all using the SCR extension.
   
   Question:
   - what is the problem for your environment when the scr association is gone
   or modified? File associations are useful for a fast and easy way of opening a
   specific file type.
4. In previous versions, the errorlevel returned could not be trusted. Will the
   new version correctly return errorlevel?
   Answer:
   - some things of kixcheck and wkixcheck are already on our TO-DO list, which
   makes it easier and more accurate to recognize your kixtart environment.
   Questions:
   - what are you meaning with "the errorlevel returned could not be trusted"? do you have
   an example?
   - did the control file kix???.ok contains the actual and correct status? can you
   run the installation with following script
   

   code:

   ---

    @echo off
     set kix-debug=ok
     %0\..\kix410update.exe /q
     rem -
     rem - rest of your script -
     rem -
    @echo off

   ---

   and return the debugging output and control file on the board or as mail.
   

• kix32 & wkix32.
  We will implement your suggestion. The kixupdate will install wkix32 at the same time.
  It can be necessary for backwards compatibility to introduce an environment variable
  for this issue.
• scr file association
  We have never think about this way of using screen saver. In a future release we will
  not influence the existing values for this scr association.
  Possible that we will implement it for our vacation in the latest final kixtart release
  (build 99).
• return codes of express package
  Les, we are always interested in the control file when the installation doesn't works
  like expected.
  Question: was it possible that you were upgrading to newer release on your windows9x
  environment.
  Possible the problem have to deal with the way data is written to disk in those
  environments. Installation script thinks control file has been removed, but it was
  still in the buffer.
  To prevent this possibility please remove first the control file(s) manually. You
  can find them in the c:\ and %windir directories.
• filecomparison
  The way you are comparing kix32.exe files will be implemented in our additional tools
  kixcheck.exe and wkixcheck too. We will use a CRC check on a related
  kixtart files. Tools will becomes flexible enough to handle also newer kixtart
  releases.
  

• implementation of "terminal service" model.
  we are using drive based on "systemroot" registry setting. it solves
  problems with unavailable C-drive.
  for the temporary files it will use as prefix %tmp% environment
  variable.
• status of file association .scr untouch by another association.
• additional information will be written to debugging file. So you can
  see what the actual registry settings for .K2K, .KIX, .SCR and .UDF are.
• script returns now also a errorlevel- 0 = a complete installation done
  - 1 = a incomplete installation done
  this value can use in your BATch file.
  f.e.
  

  code:

  ---

  @echo off
   %0\..\kix410update.exe /q
   if errorlevel 1 goto server
   if errorlevel 0 goto client
   goto server
  :server
   %0\..\kix32.exe  %0\..\your_script.kix
   goto end
  :client
   kix32 %0\..\your_script.kix
  :end
  @echo off

  ---

• in the NTx environment it isn't necessary to install the kx16.dll,
  kx32.dll and kx95.dll.
  we make it possible such installation, but for backward compatibility
  we introduce the additional environment variable kix-only-required.
  its value isn't important.
  the control file shows the result of such installation.

• kix-debug
• kix-only-required
• kix-show

• a standard installation
  

  code:

  ---

  [KiXtart]
  kix32.exe=2002/08/14 02:35:01 -> 2002/07/08 20:41:12 225280 (build 099)
  kx16.dll=2002/08/14 02:35:02 -> 2001/08/27 20:17:29 47104
  kx32.dll=2002/08/14 02:35:02 -> 2002/03/29 12:38:08 49152
  kx95.dll=2002/08/14 02:35:02 -> 2001/11/19 05:00:00 49152
  KiXtart=installation completed at 2002/08/14 02:35:02 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
  KiXtart release=ME -> kix 4.10
  KiXtart mode=registry

  ---

  kix-only-required specified.
  

  code:

  ---

  [KiXtart]
  kix32.exe=2002/08/14 02:46:02 -> 2002/07/08 20:41:12 225280 (build 099)
  KiXtart=installation completed at 2002/08/14 02:46:02 (+kix32.exe -kx16.dll -kx32.dll -kx95.dll) to "c:\windows\"
  KiXtart release=NT4 -> kix 4.10
  KiXtart mode=registry (only required files)

  ---

  -kx16.dll, -kx32.dll and -kix95.dll were removed.
  
  kix-only-required specified.
  

  code:

  ---

  [KiXtart]
  kix32.exe=2002/08/14 02:57:36 -> 2002/07/08 20:41:12 225280 (build 099)
  KiXtart=installation completed at 2002/08/14 02:57:36 (+kix32.exe ?kx16.dll ?kx32.dll ?kx95.dll) to "c:\windows\"
  KiXtart release=NT4 -> kix 4.10
  KiXtart mode=registry (only required files)

  ---

  ?kx16.dll, ?kx32.dll and ?kix95.dll aren't available on drive.
• the debugging output when kix-debug & kix-only-required are specified
  in a NTx environment:
  

  code:

  ---

  Kixtart 4.10 - NT4 debug mode (vs 3.07)               02:57:34
  
  Informative INSTALL: copy x:\kix32.exe c:\windows\kix32.exe
  
                       size.old = 225280
                       size.new = 225280
                       time.old = 2002/07/08 20:41:12
                       time.new = 2002/07/08 20:41:12
  
    company name       
    filedescription    KiXtart main executable
    fileversion        4, 10, 0, 0
    internalname       KIX32
    language           0409English
    legalcopyright     Copyright Ruud van Velsen 2002
    legaltrademarks    $
    originalfilename   KIX32.EXE
    privatebuild       
    productname        KiXtart
    productversion     4, 10, 0, 0
    specialbuild       Build 099
  
   => KiXtart - kix32.exe - 2002/08/14 02:57:36 -> 2002/07/08 20:41:12 225280 (build 099)
   => KiXtart -  - installation completed at 2002/08/14 02:57:36 (+kix32.exe ?kx16.dll ?kx32.dll ?kx95.dll) to "c:\windows\"
  Informative INSTALL: creation of KIX file associations.
   =>
   => .kix           kix32 document
   => .k2k           kix32 document
   => .scr           kix32 document
   => .udf           kix32 document
   => kix32 document Edit
   =>
   => KiXtart - KiXtart release - NT4 -> kix 4.10
   => KiXtart - KiXtart mode - registry (only required files)
  
   logevent    = Kixtart-UPDATE 3.07 script completed successfully (02:57:34 - 02:57:36) (+kix32.exe ?kx16.dll ?kx32.dll ?kx95.dll) to "c:\windows\"
  
  Kixtart 4.10 update completed. ('X:\' -> 'c:\windows\')

  ---

• the debugging output when kix-debug & kix-only-required are specified
  in a 95x environment:
  

  code:

  ---

  Kixtart 4.10 - ME debug mode (vs 3.07)               02:59:26
  
  Informative INSTALL: copy x:\kix32.exe c:\windows\kix32.exe
  
                       size.old = 225280
                       size.new = 225280
                       time.old = 2002/07/08 20:41:12
                       time.new = 2002/07/08 20:41:12
  
    company name       
    filedescription    KiXtart main executable
    fileversion        4, 10, 0, 0
    internalname       KIX32
    language           0409English
    legalcopyright     Copyright Ruud van Velsen 2002
    legaltrademarks    $
    originalfilename   KIX32.EXE
    privatebuild       
    productname        KiXtart
    productversion     4, 10, 0, 0
    specialbuild       Build 099
  
  Informative INSTALL: copy x:\kx16.dll c:\windows\kx16.dll
  
                       size.old = 47104
                       size.new = 47104
                       time.old = 2001/08/27 20:17:29
                       time.new = 2001/08/27 20:17:29
  
    company name       
    filedescription    
    fileversion        
    internalname       
    language           
    legalcopyright     
    legaltrademarks    
    originalfilename   
    privatebuild       
    productname        
    productversion     
    specialbuild       
  
  Informative INSTALL: copy x:\kx32.dll c:\windows\kx32.dll
  
                       size.old = 49152
                       size.new = 49152
                       time.old = 2002/03/29 12:38:08
                       time.new = 2002/03/29 12:38:08
  
    company name       
    filedescription    KiXtart 32 bit Thunk DLL
    fileversion        3, 61, 1, 0
    internalname       KX32
    language           0409English
    legalcopyright     Copyright Ruud van Velsen. 2001
    legaltrademarks    
    originalfilename   KX32.DLL
    privatebuild       
    productname        KiXtart
    productversion     3, 61, 1, 0
    specialbuild       
  
  Informative INSTALL: copy x:\kx95.dll c:\windows\kx95.dll
  
                       size.old = 49152
                       size.new = 49152
                       time.old = 2001/11/19 05:00:00
                       time.new = 2001/11/19 05:00:00
  
    company name       
    filedescription    KiXtart RPC client DLL
    fileversion        3, 60, 0, 0
    internalname       KX95
    language           0409English
    legalcopyright     Copyright Ruud van Velsen. 2001
    legaltrademarks    
    originalfilename   KX95.DLL
    privatebuild       
    productname        KiXtart
    productversion     3, 60, 0, 0
    specialbuild       
  
   => KiXtart - kix32.exe - 2002/08/14 02:59:31 -> 2002/07/08 20:41:12 225280 (build 099)
   => KiXtart - kx16.dll - 2002/08/14 02:59:31 -> 2001/08/27 20:17:29 47104
   => KiXtart - kx32.dll - 2002/08/14 02:59:31 -> 2002/03/29 12:38:08 49152
   => KiXtart - kx95.dll - 2002/08/14 02:59:31 -> 2001/11/19 05:00:00 49152
   => KiXtart -  - installation completed at 2002/08/14 02:59:31 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
  Informative INSTALL: creation of KIX file associations.
   =>
   => .kix           kix32 document
   => .k2k           kix32 document
   => .scr           kix32 document
   => .udf           kix32 document
   => kix32 document Edit
   =>
   => KiXtart - KiXtart release - ME -> kix 4.10
   => KiXtart - KiXtart mode - registry
  
   logevent    = Kixtart-UPDATE 3.07 script completed successfully (02:59:26 - 02:59:31) (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
  
  Kixtart 4.10 update completed. ('X:\' -> 'C:\WINDOWS\')

  ---

• a Kix410registry.exe installation when .scr has already another
  file association:
  

  code:

  ---

  Kixtart 4.10 - ME debug mode (vs 3.06)               01:30:11
  
  Informative INSTALL: copy x:\kix32.exe c:\windows\kix32.exe
  
   => KiXtart - kix32.exe - 2002/08/08 01:30:18 -> 2002/07/08 20:41:12 225280 (build 099)
   => KiXtart - kx16.dll - 2002/08/08 01:30:18 -> 2001/08/27 20:17:29 47104
   => KiXtart - kx32.dll - 2002/08/08 01:30:18 -> 2002/03/29 12:38:08 49152
   => KiXtart - kx95.dll - 2002/08/08 01:30:18 -> 2001/11/19 05:00:00 49152
   => KiXtart -  - installation completed at 2002/08/08 01:30:18 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
  Informative INSTALL: creation of KIX file associations.
   =>
   => .kix           kix32 document
   => .k2k           kix32 document
   => .scr           kix32 document test
   => .udf           kix32 document
   => kix32 document Edit
   =>
   => KiXtart - KiXtart release - ME -> kix 4.10
   => KiXtart - KiXtart mode - registry
  
   logevent    = Kixtart-UPDATE 3.06 script completed successfully (01:30:11 - 01:30:19) (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
  
  Kixtart 4.10 update completed. ('X:\' -> 'C:\WINDOWS\')

  ---

• a Kix410update.exe installation when .scr has already another
  file association:
  

  code:

  ---

  Kixtart 4.10 - ME debug mode (vs 3.06)               01:30:58
  
  Informative INSTALL: copy x:\kix32.exe c:\windows\kix32.exe
  
   => KiXtart - kix32.exe - 2002/08/08 01:31:03 -> 2002/07/08 20:41:12 225280 (build 099)
   => KiXtart - kx16.dll - 2002/08/08 01:31:03 -> 2001/08/27 20:17:29 47104
   => KiXtart - kx32.dll - 2002/08/08 01:31:03 -> 2002/03/29 12:38:08 49152
   => KiXtart - kx95.dll - 2002/08/08 01:31:03 -> 2001/11/19 05:00:00 49152
   => KiXtart -  - installation completed at 2002/08/08 01:31:03 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
   =>
   => .kix           
   => .k2k           
   => .scr           kix32 document test
   => .udf           
   => kix32 document 
   =>
   => KiXtart - KiXtart release - ME -> kix 4.10
   => KiXtart - KiXtart mode - update
  
   logevent    = Kixtart-UPDATE 3.06 script completed successfully (01:30:58 - 01:31:03) (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
  
  Kixtart 4.10 update completed. ('X:\' -> 'C:\WINDOWS\')

  ---

• the control file when you are installation kixtart files on f.e. X-drive
  

  code:

  ---

  [KiXtart]
  kix32.exe=2002/08/07 23:42:53 -> 2002/07/08 20:41:12 225280 (build 099)
  kx16.dll=2002/08/07 23:42:53 -> 2001/08/27 20:17:29 47104
  kx32.dll=2002/08/07 23:42:53 -> 2002/03/29 12:38:08 49152
  kx95.dll=2002/08/07 23:42:53 -> 2001/11/19 05:00:00 49152
  KiXtart=installation completed at 2002/08/07 23:42:53 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "x:\windows\"
  KiXtart release=ME -> kix 4.10
  KiXtart mode=registry

  ---

• Two Login scripts, for two companies logging into the same domain
• Kix3.63 already in the Enterprise
• GETTYPE.EXE and other Resource Kit utilities were not working
  properly.
• Files to be distributed were making the NTLOGON.BAT and related
  files convoluted
• Parent Company (Company A) Users were not only using the NTLOGON.BAT
  file but a secondary Batch file as well.
• Child Company (Company B) Users were running scripts from the client
  workstation and not the Logon Server.
• Groups were not be detected properly, we have added in a the “token
  cache” flush - http://helpdesk.kixtart.org/KixManual2001/Reference/GroupMembership.asp
  Also, we encountered an issue with the Infrastructure Master
  in the company.com domain.

• Locked down
• Full Administrative Access
• Domain Admins
• Servers
• Terminal Server/Citrix

code:

---

::@Echo OFF  

:: LAST EDITED; kld 10.04.02 @10:38PM pst
:: Trimmed down to use less stuff..
:: - From: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q318689
:: 3 October 2002 - Changed to Kixtart 4.02

@ECHO off 
::SETLOCAL 

VER | find "NT" > nul 
IF not errorlevel 1 GOTO Win_NT 

VER | find "2000" > nul 
IF not errorlevel 1 GOTO Win_NT 

VER | find "XP" > nul 
IF not errorlevel 1 GOTO Win_NT 

VER | find "98" > nul 
IF not errorlevel 1 GOTO Win_9X 

VER | find "95" > nul 
IF not errorlevel 1 GOTO Win_9X 

GOTO unknown_os 

:win_NT
@TITLE Company A / Company B NT Logon Script
ECHO 				HELLO %USERNAME%!
Echo 		Welcome to %USERDOMAIN%, Inc. NT Domain Environment
if not exist %SystemDrive%\Scripts\nul md %SystemDrive%\Scripts
if not exist %SystemDrive%\Scripts\kix402.ok 
%LOGONSERVER%\NETLOGON\Programs\kix402update.exe /q
%SystemDrive%\Scripts\kix32.exe %LOGONSERVER%\NETLOGON\Kixtart.kix /f
:: -- call should be reserved for calling another batch file
::%windir%\kix32.exe %LOGONSERVER%\NETLOGON\Kixtest.kix
goto end 

:win_9X
:: --- CHECK FOR FILES TO SET THE USER NAME
IF NOT EXIST %WINDIR%\PUTINENV.EXE XCOPY 
\\EOS\NETLOGON\Programs\Win9x\PUTINENV.EXE %WINDIR%
IF NOT EXIST %WINDIR%\WINSET.EXE XCOPY 
\\EOS\NETLOGON\Programs\Win9x\WINSET.EXE %WINDIR%

:: --- SET THE Environment Variables
:: -- Execute the script
::%WINDIR%\SYSTEM\KIX32.EXE %WINDIR%\SYSTEM\W95ENV.KIX

%WINDIR%\PUTINENV.EXE L
%WINDIR%\winset computername=%COMPUTERNAME%
%WINDIR%\winset username=%USERNAME%
%WINDIR%\winset LANGROUP=%LANGROUP%
%WINDIR%\winset LOGONSERVER=%LOGONSERVER%

:: --- DISPLAY THE USER NAME/DOMAIN
ECHO 				    HELLO %USERNAME%!
ECHO 		Welcome to %LANGROUP%, Inc. Windows 9x Domain 
Environment

if not exist c:\scripts\nul md c:\scripts
if not exist c:\scripts\kix402.ok %0\..\Programs\kix402update.exe /q
%0\..\kix32.exe %0\..\kix95.kix 
goto end 

:unknown_os 
:end

---

• Set some Global Variables for Registry Keys
• If a member of Company B, do some drive mappings
• Detect the OS
• If one of the Citrix Servers for Company B, GOTO specific section
  and check for ODBC, environment information and then leave
• If logging into one of the servers, leave the script
• If a member of Company A, copy some files to the client workstation
• Check for files on the workstation
• Detect what version of VirusScan, Dat, Engine, and etc. being
  reported from McAfee.
• Check to see if ePO (ePolicy Orchestrator is installed)
• Determine what time of day it is
• Build the screen for the user to let them know what is going on
• Do some common routines for all users
• Detect which subnet the user is logging in from, if from our VPN
  subnets leave
• Detect which groups the users are in and map drives and run routines
  for the users
• Routines used in Groups listed in the previous bullet