John McGuire

To find a computer in the directory (change strDomainSuffix to match your domain), once you know where it resides you can use your existing code to remove the comp from the OU, I've just pulled this from a simular script I wrote to add a comp to a group 'Code strDomainSuffix = "DC=domain,DC=co,DC=uk" Set WshNetwork = WScript.CreateObject("WScript.Network") Const ADS_SCOPE_SUBTREE = 2 Set objConnection = CreateObject("ADODB.Connection") Set objCommand = CreateObject("ADODB.Command") objConnection.Provider = "ADsDSOObject" objConnection.Open "Active Directory Provider" Set objCommand.ActiveConnection = objConnection ' Taylor this search to return the computers you want. objCommand.CommandText = "" _ & "select distinguishedName " _ & "from 'LDAP://" & strDomainSuffix & "' " _ & "where objectClass='computer' " _ & "and name='" & WshNetwork.ComputerName & "' " _ & "" objCommand.Properties("SearchScope") = ADS_SCOPE_SUBTREE objCommand.Properties("Cache Results") = False objCommand.Properties("Timeout") = 300 Set objRecordSet = objCommand.Execute objRecordSet.MoveFirst Do Until objRecordSet.EOF 'Wscript.Echo objRecordSet.Fields("distinguishedName").Value strCompOU = objRecordSet.Fields("distinguishedName").Value objRecordSet.MoveNext Loop 'This should output the path of the computer within the directory wscript.echo strCompOU 'End Code

You need to trap the error level Add "echo %errorlevel%" to your script to output the error level, in this case 0 IF ERRORLEVEL=0 goto err goto :eof :err echo error2

Just to help people out, as it took me a while to get all the drivers working I've uploaded the Pro100, Pro1000 and Broadcom drivers I've used for our Dell PC's Broadcom XP & 2000 http://www.chippers.me.uk/ris/Broadcom/ These where copied to i386 and $oem$/$1/Drivers Intel Pro100 XP & 2000 http://www.chippers.me.uk/ris/Ris100/ The i386_2k deirectory contains the i386 drivers, same driver for XP The Inst_2k is for the $oem$/$1/Drivers directory, same driver for XP Intel Pro1000 XP & 2000 http://www.chippers.me.uk/ris/Ris1000/ The i386_2k directory contains the Windows 2000 i386 drivers The i386_XP directory contains the Windows XP i386 drivers The Install directory is for the $oem$/$1/Drivers directory for 2000 and XP Server 2003 uses the XP drivers for all the above Dont forget to net stop binlsvc & net start binlsvc afterwards Hope these help Tested amd working on GX620 GX620USF GX280 GX270 GX260 GX240 GX400 D610

Running 2003 with SP1 currently on all servers

Cheers for that, I should be fine now

I plan to place a RIS server on each site, all images are flat with scripted software installs, this part is complete only bit I cant find documented is the dhcp auth part, how does it auth a specific site dhcp server or does it do all of them in the forest?

We have a test ris server in it own domain on a private lan and all the client images are working fine, just now need to set this up in the live enviroment and I'm finding it hard to get documentation on how to install it within our existing enviroment (multi site with AD and existing DHCP servers) Is it just a case of building the new RIS server in the domain and telling it not to install DHCP, or do I need to run RIS setup on existing DHCP server Anyone help?