Re: Adv Client Login Script Install

Tech-Archive recommends: Speed Up your PC by fixing your registry

The installation itself has to be run in admin context. It needs to do
create a service, create system reg keys, create files under the system
folder, etc - all requiring admin privileges.





"Les" <Les@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BB0FEFDC-2E40-43AD-8350-1C5F958EC454@xxxxxxxxxxxxxxxx
Is there a way to get this to install w/o the user having admin rights on
the
machine then with a login script then? I notice the /service switch but it
too says the user needs admin rights.

"Kerwin Medina [MSFT]" wrote:

The client installation requires that it be run in a local admin context.
What you have here is a low-rights user logging in and running the logon
script - capinst runs but has no permissions to the registry.

The push case works because we require the push account to have admin
rights
to the client machine.

"Les" <Les@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0D6EA10A-51BA-4C18-AE15-A041BA745212@xxxxxxxxxxxxxxxx
Also I should note if I do a client push with the same arguments it
works.

"Les" wrote:

I'm setting up a login script install on my test network.

The script is as follows:
ECHO ON
\\HTL-DC\NETLOGON\CAPINST.EXE /ADVCLI /SLP=HTL-SMS /ADVCLICMD
SMSSITECODE=001 CCMENABLELOGGING=TRUE CCMLOGMAXSIZE=1000000
CCMLOGLEVEL=0

(the second line is all one line, word wrap is disabled in notepad
when I
view it to verify)

I set the script up for a test user jane.doe and this is the
capinst.log:
*** Starting Installation *** - Wed Feb 15 10:33:11 2006
Unable to open the client version registry key (0).
8 Command line argument(s):
\\HTL-DC\NETLOGON\CAPINST.EXE
/ADVCLI
/SLP=HTL-SMS
/ADVCLICMD
Passing the remaining command line parameters to CCMSetup:
SMSSITECODE=001
CCMENABLELOGGING=TRUE
CCMLOGMAXSIZE=1000000
CCMLOGLEVEL=0
Checking OS Version:
Windows 2000 or greater detected.
Building SLP Query String:
This client belongs to AD Site: Default-First-Site-Name.
IP Subnets found: &ip=192.168.0.0.
IP Addresses found: &ir=192.168.0.4.
SLP HTL-SMS specified on the command line, AD will not be searched.
Checking SLP HTL-SMS for site/caps
Querying SLP:
/sms_slp/slp.dll?mp&ad=Default-First-Site-Name&ip=192.168.0.0&ir=192.168.0.4
SLP HTL-SMS returned no results, This client cannot be matched to any
site
boundaries known by that SLP
*** Installation Complete *** - Wed Feb 15 10:33:11 2006

I've tried running the script with AUTO set for sitecode and with
debuggingenabled (it didn't add any more info to the log).
I have a site boundary of AD-Default-First-Site as well as Subnet
192.168.0.0 defined (I specifically added 192.168.0.0 to the
boundaries
when
I first got the error to see if that would help). I don't have any
roaming
boundaries configured. I've copied all of the client install files
from
\\SMSvr\SMSClients to \\DC\Netlogon where my script resides.

Any thoughts as to what may be causing this error message when the IP
192.168.0.4 is in the range specified by both ADSS and SMS?





.

Relevant Pages

  • Re: need to modify local group membership via VBscript
    ... Admin run the script on all NT computers. ... script can add domain groups to the local Administrators group. ... how to add a domain group to local administrators account: ...
    (microsoft.public.windows.server.scripting)
  • Re: need to modify local group membership via VBscript
    ... domain admin credentials in the script, then run the script through the ... script would have to use alternate credentials or a third part RunAs tool. ... ' Bind to local Administrators group on remote computer. ...
    (microsoft.public.windows.server.scripting)
  • Re: need to modify local group membership via VBscript
    ... Admin run the script on all NT computers. ... script can add domain groups to the local Administrators group. ... how to add a domain group to local administrators account: ...
    (microsoft.public.windows.server.scripting)
  • Re: Redirect computers to a specific OU by IP Address
    ... Getting theIPaddress of the workstation is easy if you are running the ... script from the workstation. ... COMPLETELY lock them down until an admin put them into the rightOU. ... used for approx 180-240 days (as there is over 1000 computer accounts ...
    (microsoft.public.windows.server.active_directory)
  • Re: Domain Admin Account deleted by local Admin
    ... ou for every wise guy and enforce a group policy that contains also his ... domain account in order for him to keep his admin rights on that computer. ... >> domain admin from local administrators group. ... > Create a GPO based computer startup script that adds the "domain ...
    (microsoft.public.windows.server.active_directory)