Link to home
Start Free TrialLog in
Avatar of pgm554
pgm554Flag for United States of America

asked on

SBS 2003 Windows 7 issues

I have a W7 pro that I joined to the SBS 2003 domain and am getting popups after using the updated wizard.
The systems are all up to the latest patches.
Any ideas?
See attached captures for details.User generated imageUser generated imageUser generated imageUser generated imageUser generated image
Avatar of John
John
Flag of Canada image

The Windows 7 machine appears to be trying to run a program from the Server.  What program or EXE is in Users\fo764?
Avatar of Shaun Vermaak
That installation is part of adding computer to SBS server

On computers running Windows XP, the installation must be run from a local administrator account. On computers running Windows Vista and Windows 7, you do not need to be a local administrator. Instead, the User Account Control (UAC) asks for Administrator credentials.

This article for Windows Small Business Server 2011 Essentials but 2003 has same requirement
https://technet.microsoft.com/en-us/library/network-connection-requirements(v=ws.11).aspx
SBS2003 has long been EOL and out of support. Replace the server or at least upgrade the OS, provided the server hardware is supported by a current Server OS. Never run a server OS that is End Of Life. It is a huge security risk.

There is just no point in trying to fix your particular issue. It is a waste of your and our time.
Agree with Rindi - while it's POSSIBLE you could fix this, Microsoft is still updating Windows 7 and those updates COULD and MAY HAVE broken compatibility with the SBS 2003 server.  You need to migrate away from that technology.  It's old, it's outdated, it's horribly insecure at this point.  It's VERY unwise to continue using it.
Avatar of pgm554

ASKER

It's running a legacy app that needs to stick around for a year or two.
I have later NOS in place ,but this needs to be up and running in the meantime.

As for the app launcher located in the temp file folder,I have removed all the files from there and when rebooted ,it still looks for that file even though it's not at that path anymore.
Could there be something in the registry or perhaps a group policy that is trying to run?
ASKER CERTIFIED SOLUTION
Avatar of Shaun Vermaak
Shaun Vermaak
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of pgm554

ASKER

Seems to be a permissions issue with user.
I added to admin group and it went away.
Need to figure out have it automatically run the app as admin.