Thursday 10 May 2007

SBS 2K3 R2 - Windows Vista RipCurl (KB926505) experiences

We have been testing the SBS RipCurl - KB296505: Windows Small Business Server 2003: Vista and Outlook 2007 compatibility update - for quite a while now.

We have a number of SBS SP1 and R2 networks with Vista Business, Ultimate, or Enterprise running on them with no issues whatsoever, other than Ultimate updates via WSUS 2.0 SP1, on the SBS box or the Vista boxes. Now that WSUS 3.0 is here, any Ultimate updates will be available.

That ended yesterday. :(

The box in question is relatively new within the last 4 months. It is an Intel Pentium D based box with 3 GB of RAM running a couple of RAID 1 arrays for OS and data. SBS 2K3 R2 Premium is running on it with all recent updates applied.

In this particular case, our client had decided they wanted Vista Business on their new machines. Given our current positive experiences with Vista on SBS networks, we supported that decision. They are already running Office 2007 Enterprise OLP on their XP Pro systems.

Needless to say, a budgeted four hours for two Windows Vista workstation installs including a RipCurl of the SBS box, and an update to WSUS 3.0 went to pot. We ended up spending a whole day in there getting things working on the SBS box again, and are still dealing with some of the RipCurl aftermath on the SBS box itself. The Vista client systems are installed and running happily along.

Fortunately, no impact on employee productivity happened due to My Documents redirection, Offline Files for the Company shared folder (yes we set this up manually), and the Outlook/Exchange integration!

First, the methods for applying the RipCurl to the SBS box and then Vista:
  1. The Microsoft Document to read first: Using Windows Vista and Outlook 2007 in a Windows Small Business Server 2003 Network (Word document download). Please read it.
  2. Download and install: Update for Windows Small Business Server 2003: Windows Vista and Outlook 2007 compatibility (KB 926505).
  3. Download and install KB911829: You receive an error message when you try to perform any editing tasks, or you must click to enable the compose frame in Outlook Web Access.
  4. Download and install KB930955: Moveuser.exe is incompatible with Windows Vista and is replaced by the new Win32_UserProfile WMI functionality.
  5. ISA service Pack 2 if not installed
  6. Download and install KB930414: An update rollup is available for computers that are running ISA Server 2004, Standard Edition and Windows Small Business Server 2003, Premium Edition
  7. Download and install Firewall Client for ISA Server (Windows Vista compatibility).
  8. Proceed to manually configure certain SBS features on the Windows Vista workstation as per the above document.
The following is a screen shot of the table identifying changes to Client Application Deployment for Windows Vista on SBS:

Further to the Windows Vista client configuration: SBS Group Policy for Windows Vista

This is what the Vista GP looks like from the SBS server:

The settings look like registry entries and a lot are missing.

This is what the same GP settings look like from Vista:

But first, a warning:

Then, what GPMC looks like from Vista:

And the actual SBS - Windows Vista policy being edited for the firewall settings as per the instructions contained in the above image:

From the Using Windows Vista and Outlook 2007 ... document for editing the SBS Vista GPO from Vista:
  1. From a client computer that is running Windows Vista, log on as a domain administrator, click Start, and then type gpmc.msc in the search box.
  2. In Group Policy Management Console, click Forest:DomainName, click Domains, click DomainName, and then click Group Policy Objects.
  3. Right-click Small Business Server – Windows Vista policy, and then click Edit.
  4. In Group Policy Object Editor, browse to the appropriate GPO, and then modify the settings as needed.
  5. Click Apply, and then click OK
  6. Close Group Policy Object Editor, and then close Group Policy Management Console.
  7. To force the Group Policy settings to be applied, either run gpupdate /force from a command prompt with elevated privileges or restart the client computer.
To configure the fax service from within Windows Vista to connect to the SBS based fax service:
  1. From a computer that is running Windows Vista, open Windows Fax and Scan.
  2. Click New Fax.
  3. Click Connect to a fax server on my network.
  4. Type the name of the server that is running Windows SBS, for example \\servername. If you do not know the name of the server, click Start, type cmd, and then type set sbsserver.
  5. Type a name for the fax account, such as Server.
I tried the instruction in line 4, cmd set sbsserver in the Start Search with no results? Not too sure about that one.

And finally, there are a few caveats for the 64 bit version of Vista and shared printers. The SBS setup will not install a shared printer on Vista 64 bit along with a couple of others. It is in the document. ;0)

And finally, a Remote Assistance caveat: Remote assistance when initiated by the admin will only work Vista to Vista. If managing from an XP Pro box, it ain't gonna happen. If the user initiates a Remote Assistance request to the admin on an XP Pro box, it will work though.

I will leave the server issues to another post as it is the end of the day, and they should get more attention via an individual post.

Here is a short list of what broke:
  • MMC crashed and the wizards would not work for add/remove users, add/remove client machines, and others.
  • XP boxes can no longer be added via the mysbsserver/connectcomputer site.
  • Reports and Monitoring no longer work.
  • RWW only had Connect to my computer at work available as an option to users
  • RWW only had the above and servers available to admins.
There are a couple of other things, but I don't remember at the moment.

When doing a fairly complicated procedure, we like to make up checklists. Even if it means making up a hand drawn grid when it comes to something seemingly simple like software installation and configuration for multiple workstations. It keeps things organized and clean.

Here is a screen shot of our RipCurl checklist:

If that is something that will help you out, you can download it here: MPECS Inc. SBS-Vista RipCurl Checklist (pdf document link). Please feel free to use it for your RipCurl projects, or as a template to build your own.

Also, please let us know if there are any changes or omissions, and we will update it accordingly.

UPDATE 07-05-11: Updated the checklist to include room for client data.

Philip Elder
Microsoft Small Business Specialists


Anonymous said...

Maybe you can help us.
We have a SBS2k3 setup with ual network cards and 9 client machines running Xp PRo fine. We have just added a tenth machine with Vista Ultimate. Everything works fine apart from web surfing, half of the sites dont load properly.
If we plug this machine into the external network bypassing the sbs it works fine. Web is great.
Do you have any ideas that may help, we have applied all auto updates onto SBSmachine and Vista machine.

Many thanks,


Philip Elder Cluster MVP said...

Hi Dave,

Assuming that the RipCurl has been applied, have you monitored ISA while the Vista box is browsing the Web? Limit ISA Logging to the Vista box's IP to limit the logging traffic to that box and verify that ISA isn't causing the issue. Look for Denied or Failed connections.

Verify that the correct ISA settings are in your Internet Options settings under the Connections Tab/LAN Settings button. Also under the LAN Settings, make sure the "Use automatic configuration script" is NOT checked. We have been experiencing some issues with IE7 if that is checked.

Is the ISA client on Vista connected? And, when you open up the client and click the Test Server button you get a positive response?

What type of sites are having the issues? Are they news/data driven type sites only? Or do static sites (HTML) also experience the same difficulties?

Those are just some of the questions that come to mind without and real understanding of this particular SBS setup.

Philip E.