Client Installation

[Cybrtek2001]

Hello ALL,

Here's an easy one (I hope)... I've ran the network discovery on our site and it went well. I did not turn on the client installer because we have W'98 machines that we do not want in our new site. So currently there is a mix of OS's. My question is... Can I set up an install for our XP machines ONLY???? Remember this would be the first time we try to run any type of client install.

 

[ceigl]

I'm afraid, but cannot narrow down the automatic installation to the level of th OS

But you can use the "CCR method":
create a CCR-file for each machine you want to be installed.
The file should look like this and can be named anything.ccr:

[NT Client Configuration Request]
Machine Name=Client0815

By manually creating the .CCR and placing it in the ccr.box on the CAP, you do not need any discovery method enabled or any installation method enabled.

Do this for every machine you want SMS to install.
I use this method in our productional environment and till now did not experience troubles.

After the XP RIS-Installation I do the following:
I autologon a user who installs needed SW and as a final step a so-called "inst_sms.cmd" is executed...
_____
copy s:\autoinstall\blankccr.txt c:\%computername%.ccr
echo Machine Name=%computername% >>%computername%.ccr
copy *.ccr \\SMS_SERVERxxx\CAP_xxx\ccr.box
(The file blankccr.txt only contains [NT Client Configuration Request])
_____


Hope, this helps !
Chris

 

[sambusa]

but brother what u mean by s:\autoinstall...
i think u mean to copy the file blankccr.txt from any media ..floppy... to the server...

explain pls
sorry

 

[puterdude01]

Cybrtek2001,
I have a mixture of windows 2000, NT and 98 and only want 2000 machines as clients. What I did was add a line in the login script that calls another script which checks the os version and if nt 5 then check to see if there is an winnt/ms/sms/clicomp/hinv folder if so exit if not them run the smsls.bat from a specified location.

 

[tonyl02]

You could try writing a kix script that detects OS and runs the install if XP...

 

[jbrunnqu]

Once you have completed network discovery and the SMS database has been populated, deleted any records you do not want the SMS client installed on and then enable windows remote nt installation. Clients will have to be in the correct domain be in a valid subnet and have an sms record to be installed.

 

[wrarmykeys]

I use an if / then statement in our logon script to deply clients. The same structure could be used while making an exception for any o/s other than XP.

'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
'Determine OS
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
OS = WshProcessEnvironment("OS&quot
If OS <> &quot;Windows_NT&quot; Then
OS = &quot;Win32&quot;
WshLogonServer = &quot;\\<Domain Controller>&quot;
WshLogonPath = WshLogonServer & &quot;\netlogon&quot;
WshInstall = WshLogonPath & &quot;\Bin\&quot;
EnvWinDir = WshProcessEnvironment(&quot;windir&quot
WshSys32 = EnvWinDir & &quot;\system\&quot;
End If

If UseNTServer = &quot;yes&quot; Then
If OS = &quot;Windows_NT&quot; Then
WshLogonServer = WshShell.ExpandEnvironmentStrings(&quot;%LOGONSERVER%&quot
WshSysRoot = WshShell.ExpandEnvironmentStrings(&quot;%SYSTEMROOT%&quot
WshLogonPath = WshLogonServer & &quot;\netlogon&quot;
WshInstall = WshLogonPath & &quot;\Bin\&quot;
EnvWinDir = WshProcessEnvironment(&quot;windir&quot
WshSys32 = EnvWinDir & &quot;\system32\&quot;
End If
Else
If OS = &quot;Windows_NT&quot; Then
If WshShell.RegRead (&quot;HKLM\SYSTEM\CurrentControlSet\Control\ProductOptions\ProductType&quot = &quot;WinNT&quot; Then
WshLogonServer = WshShell.ExpandEnvironmentStrings(&quot;%LOGONSERVER%&quot
WshSysRoot = WshShell.ExpandEnvironmentStrings(&quot;%SYSTEMROOT%&quot
WshLogonPath = WshLogonServer & &quot;\netlogon&quot;
WshInstall = WshLogonPath & &quot;\Bin\&quot;
EnvWinDir = WshProcessEnvironment(&quot;windir&quot
WshSys32 = EnvWinDir & &quot;\system32\&quot;
Else
Dim Box
Box = MsgBox (&quot;Will NOT run WSH Login Script on a Windows NT Server - Exiting Logon Script!&quot;, 64, &quot;Login to &quot; & RHCMASTER)
WScript.Quit
End If
Else
'
End If
End If

Hope that helps

 

[Cybrtek2001]

Hello ALL,

A big thanks to you all who have replied to this thread with suggestions. I went ahead and enabled Windows NT Remote Client Installation and narrowed it down to NT Workstations only, which was good enough for what I wanted to do. Unfortunately I am not part of the network group and do not fully understand or have access to logon scripts.

CHRIS71 - I was hoping that you'd go over the manual creation on .ccr files. So if I create a .ccr file, lets say named sw-cala-tbcjdom.ccr (which is our naming convention here), do I simply just put it in the ccr.box and that's it? Also, can you explain the second part that you do, which talks about the XP RIS installation???

The reason why I ask is because most machines are being discovered and installed, but there are the few that have been discovered but not installed. Same HW, same OS, same image, same deploy procedure, but not installed.

Oh, and one more thing - Anybody have any idea why laptops would be discovered BUT client not installed??? This is happening with all of our laptops, which are on a dock. We have IMB Thinkpads, Dell Latitudes, and Toshiba 7220's.