Re: RPC error with Logon Script
- From: Meinolf Weber <meiweb(nospam)@gmx.de>
- Date: Sat, 22 Mar 2008 14:30:28 +0000 (UTC)
Hello aaron,
Did you check "Always wait for the network at computer startup and logon" for the clients in GPO. Maybe this helps. Seems tht the network is not complete prepared before the script runs.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
We have a simple three line vbscript that adds a default printer for a
user when they log in:
Set objWSHNet = CreateObject("WScript.Network")
objWSHNet.AddWindowsPrinterConnection "\\PRINTSERVER\A_Printer"
objWSHNet.SetDefaultPrinter "\\PRINTSERVER\A_Printer"
We have used this script successfully for years and years. Today,
though, we moved printing services on to a new server. The only
change we made to the script is changing the server name to the new
server. Now, when a user logs in for the first time, it attempts to
run that script and we get a "Remote Procedure Call Failed Error
#800706BE".
If the user, after getting to the desktop, runs this VERY SAME script
by hand...it works. Further, if that user logs out, and another user
logs in, the script will run at log in for that second user just
fine!! o_0
It's almost as if, the first time it attempts it, it can't find the
server, but then it can on the second and subsequent attempts, but I'm
unsure why that would be. Anyone have any thoughts?
.
- Follow-Ups:
- Re: RPC error with Logon Script
- From: Aaron
- Re: RPC error with Logon Script
- From: Aaron
- Re: RPC error with Logon Script
- References:
- RPC error with Logon Script
- From: Aaron
- RPC error with Logon Script
- Prev by Date: Re: Windows Server 2003 stops responding
- Next by Date: Re: Intel PRO 1000 PM, VLAN's, LinkSys SRW 2024
- Previous by thread: RPC error with Logon Script
- Next by thread: Re: RPC error with Logon Script
- Index(es):
Relevant Pages
|