Re: Logon scripts don't run on 64-bit machines?

Tech-Archive recommends: Fix windows errors by optimizing your registry

On Mon, 5 Nov 2007 02:59:01 -0800, musosdev wrote in
microsoft.public.scripting.wsh:

Thank you all for your ideas and replies so far. I'm still no further.

I ran the cscript at the cmd prompt on the 64-bit workstation just now and
here is the output......

--------------------------------------------------------------------------------
Microsoft Windows [Version 5.2.3790]

Windows Server 2003?

(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\dhnash>cscript //D
\\boris\SYSVOL\thepoint.org.uk.loca
l\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\USER\Scripts\Logon\MM_logon.vb
s
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

\\boris\SYSVOL\thepoint.org.uk.local\Policies\{31B2F340-016D-11D2-945F-00C04FB98
4F9}\USER\Scripts\Logon\MM_logon.vbs(31, 1) ADODB.Connection: Provider is
not sp
ecified and there is no designated default provider.


C:\Documents and Settings\dhnash>cscript //D
\\boris\SYSVOL\thepoint.org.uk.loca
l\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\USER\Scripts\Logon\hnPrinters.
vbs
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

\\boris\SYSVOL\thepoint.org.uk.local\Policies\{31B2F340-016D-11D2-945F-00C04FB98
4F9}\USER\Scripts\Logon\hnPrinters.vbs(31, 1) (null): The printer driver is
unkn
own.
--------------------------------------------------------------------------------

I'm a little confused with both scripts to be honest. Firstly, the ADODB
error - we can get to the SQL Server (Start > Run ? '\\sqlserver'), and our
Intranet (which is located on IIS on the SQLServer machine, and obviously
uses SQL as the database) works perfectly. And yet, the logon script can't
access it. All other machines (non 64-bit) work perfectly.

The printers script is even more strange - the printers are installed on the
DSERV (we have 3 servers.. Boris is PDC, DSERV and ATLAS are replicated), and
the script uses \\dserv\\printer_name to connect to each printer. We then
select whichever one to be the default depending on which computer is logging
on.

Again, this works fine on non 64-bit machines, but gives the "no printer
driver" error on the 64-bit ones.

Any help is GREATLY appreciated. I have included the scripts below for
convenience.
[snip]

Microsoft Windows [Version 5.2.3790]
This seems to be Windows Server 2003; my own very limited experiences is
with NT6.0.6000.16386 (Vista) 64-bit, so I'm not sure how much of the
vague points below apply at all.

Without delving into the code, although posting it was the right thing
to do, two things come to mind:

1) seems to indicate that there is no 64-bit ODBC driver; try to run
CSCRIPT.EXE from SysWOW64 and/or see what SysWOW64\ODBCAD32.EXE versus
System32\ODBCAD32.EXE show.

2) might indicate that there is no 64-bit driver for those printers, or
that the demarcation of login scripts for local administrators with UAC
kicks in. Installing 64-bit printer drivers on a 32-bit print server is
a challenge.

--
Michael Bednarek http://mbednarek.com/ "POST NO BILLS"
.

Relevant Pages