I have a Vista Business client and I'm trying to install it onto an SBS 2003 Premium box. The SBS has Windows Server SP2  and ISA SP3 installed. I've also installed the KB926505 on the server and KB930955 on the Vista machine.

 

The problem I'm having is that when I run connectcomputer I get a warning message up about SBS Metwork Configuration Wizard - An error occured while trying to copy the Client Setup files. Check the following...

 

It mentions a proxy server and although ISA is installed it shouldn;t be affecting the Vista machine as the LAN settings are clear (no ISA entries). The other part of the message goes on about reinstalling the Client Deployment component and within the SBSVista_Conceptual documentation from MS there is a mention:

 

Important
After you install the "Update for Windows Small Business Server 2003: Windows Vista and Outlook 2007 compatibility (KB 926505)," if you run Windows SBS Setup from Add/Remove programs for Client Deployment tools to either reinstall or in maintenance mode, you must reinstall the update on the server.

Not sure if my head is on straight here but what does this mean? When I look at this I cannot fathom what it's asking me to do. I assume it wants me to reinstall the client deployment component on the server but can anyone give me a heads up on how to perform this task?

 

Thanx

I think that is saying that if for some reason you rmoved or reinstalled the client deployment you have to run the update again. You run it again by just clicking on the downloaded file for kb926505. If you run it and it says it cannot install it than it is already installed properly.

 

To get Vista to join, I would try ~

Try to run kn926505 again

Removed the Computer Account from SBS

Recreate the computer account on SBS

put Vista back into a workgroup

deleted the "__sbs_netsetup__" from Vista

turned off UAC on Vista

 

I have had instances where Vista got totally confused after a couple of failed attempts to join and I had to reinstall it before it would join.

Thanx for the advice Stan. I'll give this a go. One thing that does trouble me though is that the Vista client doesn't even seem to get onto the starting blocks in the scenario. The error comes up when you try and run the nshelp.exe(? I think that was what it was called) application window that pops up when you try accessing connectcomputer...you don't even get a chance for the Vista client to touch the domain so there's been no username or workstation info passed from the domain at this point.

 

Very strange. I'll also try the Client Deployment reinstall...one thing I do know though is that on both occassions I've seen this I've not had Outlook 2003 installed on the server for deployment and I'm wondering if the KB926505 new deployment upgrade is actually expecting this in some way?

Hi again

 

Apologies for taking so long in getting back about this problem but other items came first but I'm now back trying to sort this. I've tried to reapply KB926505 and it does appear to run but I note that the toolbar only appears to go up partially before it comes up with the close window option.

 

Now I note that both the clients I'm experiencing the problem on only have certain apps within the ClientApps folder (for space saving resons and the fact these clients all have Office 2003/2007 installed - no need for Outlook to be in the ClientApps). Could not having all the apps in the ClientApps folder be a problem? If so how do I 'reinstall' these apps before reapplying the KB article fix? I'd assume I need to access Add/Remove Programs on the SBS and then Change/Remove Windows Small Business Server 2003; run the wizards and then pick what I'd like installed as such but I've not had to do this before and would appreciate some guidance on this part. Will there be a need for a reboot of the server (therefore needing to be done out of hours). I'm also concious that there are certificates, etc in the ClientApps folders and will thee be replaced or should I create a copy before doing this?

 

Thanx for any advice.

Hi Steve,

 

SBS Setup, set it to Maintenance mode, and select the Clientapps to reinstall. That in itself doesn't need a reboot, however, if you have non SP1 integrated media, you would need to reapply SBS 2003 SP1, which will need a reboot.

Thanx Marina

 

The original install did use non SP1 discs so looks as though I may need to reinstall SP1 again as you suggest. However, the client also has R2 discs and I was wondering if these could be used (even though the server isn't R2) or would this merely confuse matters?

Marina

 

If I go down the root of reinstalling the clientapps from the non SP1 media then you mention I need to reinstall SBS SP1. I assume this is only SBS SP1 and not everything else that came with it (Exchange SP1, etc) as I've already moved these forward to SP2 and further for ISA, etc?

 

Thanx

Hi Steven,

 

You can't uninstall SBS 2003 SP1. Are you running it as the built-in Administrator?

Hi Steven,

 

Do you have an additional Domain Controller?

Hi Steven,

 

Do you have a healthy replication between the SBS and the other DC? The error you get about the domain admin etcetera can occur when you are not installing SBS 2003 SP1 as the built-in administrator, when the SBS can't contact the other DC or when the administrator has memberships in groups that shouldn't be assigned to the administrator.

Hi Steven,

 

Sorry, have been busy and still am. Remove all groups that aren't necessary. Check the SBS 2003 SP1 doc for the only groups needed to be able to run that SP. When the SP is installed successfully, you can if you really need to, add those groups back in. Although I am wondering about the IIS_WPG group being there.

Appreciate the time you're putting in here helping me out...I know how busy you are. I've done some further checking and have found a replication problem between the SBS and the remote DC. On the remote DC I get a couple of DNS errors after running dcdiag /test:dns. The are:

 

Forwarders list has invalid forwarder: 208.67.22.220