IT_Architect
asked on
SBS 2003 attempts to apply server SP to Vista after login
SBS 2003 Network.
I have several 2003 and 2008 networks out there, but nothing like this happens on any of the others. Every time a client logs in they get a dialog box that says:
A program needs your permission to continue
If you started this program, continue.
Windows Small Business Server 2003 with Service Pack 1
Microsoft Corporation.
[Continue] [Cancel]
The issue has been there since day one of the install. Since you cannot turn off rolling out service packs, and it's trying to roll out a server service pack to Vista, it is a problem caused by 2003 server, but how do I get rid of it?
bug.jpg
I have several 2003 and 2008 networks out there, but nothing like this happens on any of the others. Every time a client logs in they get a dialog box that says:
A program needs your permission to continue
If you started this program, continue.
Windows Small Business Server 2003 with Service Pack 1
Microsoft Corporation.
[Continue] [Cancel]
The issue has been there since day one of the install. Since you cannot turn off rolling out service packs, and it's trying to roll out a server service pack to Vista, it is a problem caused by 2003 server, but how do I get rid of it?
bug.jpg
Abbas Haidar
logon as a user with admin permissions, it will install the pack and then you can work normally.
ASKER
Let me see if I understand this. If I log in as administrator on the Vista Workstation, it will install the SBS 2003 SP1 on the Vista Workstation, and everything will be all better?
Do you have anything in the event logger? Please attach it here
this is the sbs installation files software pack not the service pack
It sounds to me as though something got changed to the Client Setup Settings in the SBS Management Console.
From the Management Console, click on Client Computers and then "View Computer Settings".
For each Vista Machine, expand the "Client Setup Settings".
It should look like the attached image, and specifically it should be set to NOT allow users to modify assigned applications.
The other possibility is that you have never installed the Vista compatibility update to the SBS 2003.
Info on that here: http://support.microsoft.com/kb/926505
Jeff
TechSoEasy
sbsclient.jpg
From the Management Console, click on Client Computers and then "View Computer Settings".
For each Vista Machine, expand the "Client Setup Settings".
It should look like the attached image, and specifically it should be set to NOT allow users to modify assigned applications.
The other possibility is that you have never installed the Vista compatibility update to the SBS 2003.
Info on that here: http://support.microsoft.com/kb/926505
Jeff
TechSoEasy
sbsclient.jpg
ASKER
>Do you have anything in the event logger?<
Nothing. (I had to wait until they went home for the day.) This is odd. It cannot be that common because I don't see it on Google Searches. I'm going to dig the registries.
Nothing. (I had to wait until they went home for the day.) This is odd. It cannot be that common because I don't see it on Google Searches. I'm going to dig the registries.
Did you verify that the Vista Compatibility Hotfix has been installed?
Because that error message you are getting is specifically detailed in the KB article I listed above:
You should be logging onto the Vista machine with a domain admin account to get the updates correctly on the client after the hotfix has been installed on the SBS.
Jeff
TechSoEasy
Because that error message you are getting is specifically detailed in the KB article I listed above:
Note If you used the previously published steps to manually join the Windows Vista-based computer or the Windows 7-based computer to a Windows SBS network, you must log off and then log back on to the client computer after you install the update. You will receive a one-time User Account Control (UAC) prompt for SBS 2003 SP1 before the client is updated with the correct settings.
You should be logging onto the Vista machine with a domain admin account to get the updates correctly on the client after the hotfix has been installed on the SBS.
Jeff
TechSoEasy
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
any update on this?
Jeff
TechSoEasy
Jeff
TechSoEasy
Download autoruns from Microsoft and check if there's anything related in there in the start up. check the logons, scheduled tasks, drivers... etc
to better analyse, you can share with us the result so we can check if there's anything as well.
http://www.filehippo.com/download_autoruns/
to better analyse, you can share with us the result so we can check if there's anything as well.
http://www.filehippo.com/download_autoruns/
No reason to do that... it's the SBS_LOGIN_SCRIPT.bat that has the setup.exe command.
Jeff
TechSoEasy
Jeff
TechSoEasy
ASKER
I'm back. I'm not on site. It's working hours at the moment, but I'm going to check if they have anyone who is off today and I'll RDP in an use their machine. Else, I'll wait until tonight and try them. All I know is I have plenty of SBS out there and I've never had to track something down like this before.
Thanks!
PS: I tried to attach a 12K png and then as a jpg, but the server doesn't want to take it at the moment.
Thanks!
PS: I tried to attach a 12K png and then as a jpg, but the server doesn't want to take it at the moment.
ASKER
Did you verify that the Vista Compatibility Hotfix has been installed?I tracked that one down. The KB was installed. Whether I log in as the administrator or the user, I get the same thing every time. This has been tried dozens of times.
Because that error message you are getting is specifically detailed in the KB article I listed above:
It should look like the attached image, and specifically it should be set to NOT allow users to modify assigned applicationsThe only thing it says to install is the Fax client and service packs.
And if all else fails, remove (or REM) the executable line from the SBS_LOGIN_SCRIPT.bat file that runs setup.exe. That's what's causing the prompt in the first place.I did, and that works. LOL! I guess I'll go with that.
Thanks!
ASKER
It wouldn't be honest to give it an A because it's a work-around. However, his logic is sound, and nobody worked harder to solve this mystifying anomaly. Until someone comes up with something that accurately defines and solves this problem, this is a valuable solution, and belongs in the database. Thanks Tons!
Its not a workaround. The fact of the matter is that the life-cycle has ended on SBS2003 and this is really the only option to resolve the problem.
Jeff
TechSoEasy
Jeff
TechSoEasy
ASKER
Hi Jeff,
>Its not a workaround. The fact of the matter is that the life-cycle has ended on SBS2003 and this is really the only option to resolve the problem.<
That doesn't make sense to me. I agree that I can't go to Microsoft for support on it, but until very recently, I had other SBS 2003 R2 servers, and they didn't have that problem. What do you mean?
>Its not a workaround. The fact of the matter is that the life-cycle has ended on SBS2003 and this is really the only option to resolve the problem.<
That doesn't make sense to me. I agree that I can't go to Microsoft for support on it, but until very recently, I had other SBS 2003 R2 servers, and they didn't have that problem. What do you mean?
The entire nature of how application deployment, group policy, patches and the like has changed. So you have a 10-year-old server trying to communicate with 2-year-old clients which work very differently than their predecessors.
How many of the other SBS 2003 R2 servers had Vista or Win7 clients? Because that's the issue. Since Microsoft isn't supporting SBS 2003 anymore, they aren't providing the proper fixes to make it work with the latest client OS's. Therefore, you have to provide that fix yourself.
Jeff
TechSoEasy
How many of the other SBS 2003 R2 servers had Vista or Win7 clients? Because that's the issue. Since Microsoft isn't supporting SBS 2003 anymore, they aren't providing the proper fixes to make it work with the latest client OS's. Therefore, you have to provide that fix yourself.
Jeff
TechSoEasy