• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 593
  • Last Modified:

Windows 2003 Server & Windows 7 Pro 64 Bit

Logging any client into the SBS 2003 domain runs setup.exe from the server.  This may be something to do with AD, but I cannot be sure.

My client has purchased a Windows 7 64 bit PC (little else available) and whilst it works on the domain perfectly, every time someone logs in the error message that 'setup.exe' from the server is incompatible appears.  It is easy to cancel and does not seem to create any issues, but it is an annoyance.

Of course it is obvious that a 32bit piece application from the Server will not run in the W7 64 bit environment, but I cannot find anyway of stopping the W7 64bit system trying to run it.

Any ideas?
0
davesheppard
Asked:
davesheppard
  • 2
  • 2
2 Solutions
 
Chris MillardCommented:
setup.exe is called as part of the SBS_LOGIN.BAT file. If you check the account of any domain user in active directory users and computers, you will see the SBS_LOGIN.BAT in their account.

What you COULD do, is modify the batch file to only run certain commands (including setup.exe) if a certain version of Windows is detected.

See this page for an example of how to check which version of Windows is running:-

http://www.grimadmin.com/article.php/batchfile-easy-way-to-detect-os-version
0
 
davesheppardAuthor Commented:
Many thanks Roy, just before setting the remote access to this client, is the SBS_LOGIN.BAT file on the Server or on the PC.
0
 
dstewart785Commented:
roybridge is correct in his explanation to the whereabouts of the SETUP.EXE call. Also, the fix is to not run the command line on a 64 bit machine, but you may want to run the remaining script. The easiest way to do this is to have any 64 bit machine bypass the command and continue down the logon batch file.

Operating systems maintain a set of variables to describe the machine and OS in use.  If you use the DOS command SET from a DOS window, you will see all the values set on your machine. The value to determine the architecture (32 or 64 bit) for command scripts (DOS) is PROCESSOR_ARCHITECTURE. A 64 bit machine will show PROCESSOR_ARCHITECTURE=AMD64 while a 32 bit machine will show PROCESSOR_ARCHITECTURE=x86. Using this information, you can add some lines to your logon script to step by the SETUP Command:

1. Browse to the logon script file at \\sbsservername\netlogon, and open the logon script for editing

2. Locate the command \\sbsservername\clients\setup\setup.exe /s sbsservername

3. Insert a line above it:

 IF "%PROCESSOR_ARCHITECTURE%"=="AMD64" GOTO MissSetup

4. Now, insert a line below the setup.exe command line found in step 2:

:MissSetup
 (include the : in the line)

Your logon script should like:

                     IF "%PROCESSOR_ARCHITECTURE%"=="AMD64" GOTO MissSetup
                     \\sbsservername\clients\setup\setup.exe /s sbsservername
                     :MissSetup

5. Save it.

NOTE: You may have to log onto the SBS server itself as Administrator and locate the logon script in C:\Windows drive in order to edit it.

Now, during the logon process, when any machine running 64 bit architecture gets to the IF EXIST command line, it will skip to the :MissSetup line, bypassing the \\sbsservername\clients\setup\setup.exe /s sbsservername line

Sorry about the education if you were just looking for the answer.
0
 
Chris MillardCommented:
@davesheppard - the SBS_LOGIN.BAT is on the server.
0
 
davesheppardAuthor Commented:
Many thanks to you both, it worked perfectly.  I have split the points as I needed you both, hope neither of you mind.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now