Showing posts with label SBS 2003 R2. Show all posts
Showing posts with label SBS 2003 R2. Show all posts

Friday, 23 July 2010

Amazing WSUS v3 Cleanup Wizard Time Now Into Days!

We started the cleanup wizard on our managed SBS 2003 boxes three days ago.

All of the boxes finished in anywhere from 18 hours to 36 hours later.

We have however, one box that is _still_ running its cleanup process.

Now, this is not one of our normally crusty boxes as it is under 2 years old and is running a quad core Xeon X3220 with 4GB of RAM. Its reports normally come in every morning on time.

Since starting the wizard the reports have stopped, but we left the wizard alone just in case.

It took _two full days_ for the wizard to gain and hold just one pip on the progress bar.

So, here we are three mornings later:

image

We now have a number of pips in the progress bar but the process is still moving quite slow.

On the other boxes, the SQL process handling the cleanup usually pins a core on the server. In this case the SQL process has barely taken any additional headroom on the CPU.

image

Judging by the CPU time allotment shown in the above Task Manager Processes tab new the cleanup process is running however slowly.

If we have not seen at least three or four additional pips on the progress bar we will reboot this box tonight and restart the process.

We track the progress by setting a Notepad window above the progress bar and noting the advances of the progress bar:

image

The WSUS V3 Cleanup Wizard may look like it is not working even when checking the SQL Process CPU usage in the Task Manager, but in this case we let it ride and things started to move after a day!

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Saturday, 30 January 2010

SBS 2003 R2 – WSUS SP Blue Shield Fix

We had one of our SBS 2003 R2 Premium boxes go blue shield on us after WSUS v3 was service packed.

As we combed through the various settings to make sure they were set to the SBS 2003 R2 specific ones, we ended up needing to recreate the groups in the WSUS console, set the Products updated to all, and reset the sync schedule to automatic.

After combing through all of those settings though, we still had a blue shield.

The fix ended up being the SQL script that we needed to run in the following Knowledgebase article under the second method:

After running the script we received the following output:

Changed database context to 'SUSDB'.
Using SUSDB
No work to do.  Record already exists.
Automatic Approval For Detection is already enabled
Target group of approval for detection is not "AllComputers"
Inserting "AllComputers" group
"AllComputers" Group added
Critical update is not in approval for detection classification
Critical update is inserted to approval for detection classification
Security update is not in approval for detection classification
Security update is inserted to approval for detection classification
Service pack is not in approval for detection classification
Service pack is inserted to approval for detection classification

We then went into the SBS Console and clicked on the Update Services node and after a few minutes were greeted with:

image

We now have our WSUS integration back.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Wednesday, 2 December 2009

WSUS – Error 33002 – Access to module dbo.spConfiguration is blocked because the signature is not valid

This one has showed up on a few of our WSUS v3 based SBS 2003 R2 boxes after the last post update reboots. And, there are _lots_ of them:

Event Type:    Error
Event Source:    MSSQL$MICROSOFT##SSEE
Event Category:    (2)
Event ID:    33002
Date:        12/1/2009
Time:        5:40:43 PM
User:        NT AUTHORITY\NETWORK SERVICE
Computer:   SBS
Description:
Access to module dbo.spConfiguration is blocked because the signature is not valid.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Another example of the error:

Event Type:    Error
Event Source:    MSSQL$MICROSOFT##SSEE
Event Category:    (2)
Event ID:    33002
Date:        12/1/2009
Time:        5:40:43 PM
User:        NT AUTHORITY\NETWORK SERVICE
Computer:    SBS
Description:
Access to module dbo.spReturnStateMachineTransitionEventLogEntriesFromError is blocked because the signature is not valid.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The only thing to come up in our searches to fix the problem were to do the following:

  1. Start –> Run –> Services.msc [Enter]
  2. Right click and Restart Windows Internal Database.
  3. Right click and Restart Update Services.
    • image
  4. Verify that there are no more errors in the logs.

The solution was found on Experts-Exchange: Event ID: 33002 Access blocked because signature is not valid.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Friday, 5 June 2009

SBS 2003 to SBS 2008 Migration Stall – Update – A Little More Confidence Now

We have put a lot of time into a failed SBS 2003 to SBS 2008 migration.

We have since initiated a support incident with Microsoft’s Product Support Services (PSS). We spent about 4 hours working with the first support engineer which lead us nowhere.

Needless to say, there was not a lot of confidence going into the second round that was an escalation from the previous day when we were contacted by PSS yesterday.

We did not want to burn another 4 or more hours, it ended up being the whole day, babysitting the PSS remote session and come to a point where we were no further ahead.

It is very important to note that in this case we were able to have a ShadowProtect image sent up to us and we were able to restore that image on a server here and replicate the error by running the migration process on our lab servers.

Why is that important?

Because, when we finally spoke to Edwin at the end of yesterday’s seemingly nonproductive support session and expressed frustration with the situation, he came around and explained what they were able to discover by being able to DCPromo the SBS 08 box out of the SBS 03 domain and DCPromo it back in again.

The lab has provided the support team with unfettered access to the problematic domain without impacting productivity on the production SBS domain! And, as a result, they were better able to pinpoint what they think is the source of replication errors between SBS 2003 and SBS 2008 by DCPromoing .

This morning, in my discussion with Edwin as we began the next round of troubleshooting, I mentioned my MVP status and he asked me if I had heard of his recent document on SBS 2000 to SBS 2008 Migration (document download page)!

Edwin Anthony Joseph (his blog) is the lead engineer that we are working with. And yes, I mentioned that I have heard and read his document and that it is an excellent methodology for migrating from SBS 2000.

So, today, Edwin is working with some additional team members that are tied into Active Directory and replication. Hopefully, by the end of today we will have the source of the problem and the steps needed to fix it on the actual source SBS 2003 network!

Needless to say, we are a lot more confident that we are going to come through this with a positive result.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)

Windows Live Writer

Monday, 21 April 2008

SBS 2003 R2 - Setup steps and resources - Revised V2.1.1

This is a revision of the original post: SBS 2K3 R2 - Setup steps and resources.

It has been updated to include some new functionality as well as some available feature additions that can be installed during the various stages of the setup.

  1. Install the base OS to the primary OS drive formatted leaving 10 GB unused on the drive during setup. All other drives/partitions should be left untouched at this time.
  2. Stop the continuing setup after the reboot by cancelling it.
  3. In between Phase 1 and Phase 2: Install relevant drivers, format the partitions and drives.
  4. Install the following Windows Server Tools:
  5. Move the Swap File over to the partition created out of the above 10 GB. This partition can be used for the ISA URLCache as well.
  6. Verify all devices are recognized and happy.
  7. Run Phase 2 setup via the Setup icon on the desktop.
  8. We set the MSDE Engine, Users Shared Folders, Client Applications, and Sent Faxes to the same drive/partition.

  9. After the final SBS reboot, enter the Domain Admin account into the DHCP Manager's properties.
  10. Finish the install by completing the ToDo tasks.
    • OPTION: Install Access Based Enumeration for greater folder security. Enable ABE by share as opposed to globally.
    • OPTION: During the CEICW add the following attachment extensions to the Exchange exclusion list: .htm .html
    • OPTION: Revise your user template Quotas as appropriate by right clicking your data drive --> Properties --> Quota --> Quota Entries and change the template volume.
    • OPTION: Download and install .NET 2.0 in preparation for SyncToy.
      • OPTION: Download and install the Microsoft copy utility: SyncToy 1.4.
  11. Install the Premium Technologies with SQL Server 2005 Workgroup Edition followed by ISA 2004 SP1.
  12. Install ISA 2004 via the Premium Technologies CD
    • The CEICW will fail on the initial ISA install. ISA SP2 or later will fix that.
    • Note that during the ISA CEICW one will need to recheck any extra settings at the Web Services Configuration step as it tends to pull them back.
    • Make sure that the Create Certificate is also left at the setting it chooses.
  13. Install the components and updates from the R2 Technologies CD.
  14. Install IE7 for Windows Server 2003 (download link).
  15. Complete the Post Exchange SP2 Must Dos (previous blog post).
  16. Enable Exchange settings: "Display routing groups" and "Display administrative groups" by righ clicking on the Exchange "First Organization" --> Properties and tick both. Apply & OK.
  17. If there are no pre-Exchange 2000 servers on the domain switch to "Native Mode" while in the above Properties.
  18. Look at the client email Mailbox size limits. We tend to set the limit to 1GB out of the box.
    • Under Advanced Management: MySBSDomain (Exchange) --> Administrative Groups --> first administrative group --> Servers --> MySBSServer -->First Storage Group --> Right click Mailbox Store (MySBSServer) and Properties --> Limits Tab.
  19. Update the Exchange registry settings for the Greylist problem that Exchange seems to be having: Exchange may not be retrying! (previous blog post)
  20. Impliment Recipient Filtering to protect against a Reverse NDR Spam Attack (previous blog post) and avoid an SMTP Queue Length error in the inbox.
  21. Install WSS 3.x in side-by-side mode (official SBS blog post on the matter). Why? Because the WSS 3.x and Outlook two way functionality may be required for WSS hosted calendars, or the Recycle Bin may be for those who "accidentally" delete files.
  22. Install WSUS 3.x afterwards (previous blog post on WSUS 3.x install experience).
    • Note that WSUS v2 should be synchronized before installing WSUS v3.
  23. At the command prompt, run the appropriate osql commands to tame SQL's memory usage (previous blog post explanation).
  24. RipCurl the SBS R2 box for Vista and Office 2007 compatibility (previous blog post).
    • ISA SP3 to follow the RipCurl Patch for ISA
  25. Uncheck "Shutdown worker processes after being idle for (time in minutes)" under the Performance Tab for the DefaultAppPool in IIS.
    • This reduces the first visit to Companyweb browser stall in the morning.
  26. Setup any Software installs via Group Policy (previous blog post) making sure to modify the permissions on \ClientApps\.
  27. Create and setup any custom Domain or OU level Group Policy Objects.
    • We remove a domain user's ability to remotely shutdown any system as one example.
  28. OPTION: (May not be needed if you plan to use WSS v3 as principle) Upgrade the Companyweb SharePoint MSDE instance to SQL 2005 (smallbizserver.net article) and enable Full Text Search.
  29. OPTION: Backup the server using your preferred backup method. Ours is StorageCraft's ShadowProtect. Crash the drives. Restore from backup and then deliver.
  30. OPTION: Enable users ability to change their password while working in Outlook Web access (OWA) (previous blog post).
    In the case of the R2 Tech CD, verify that the Service Packs are still current before installing. If not, download and install the most current Service Pack.

    Post Updates:
    • 2008-01-18: Added steps 4a, 4b, and 4c above to download and install the appropriate support tools.
    • 2008-02-15: Added the step to implement Recipient Filtering in Exchange to avoid SMTP Queue Length errors and protect against a Reverse NDR Spam Attack.
    • 2008-03-24: Added IE 7 for Server 2003 download link and install recommendation. Also added the link to SyncToy 1.4 to download and install.
    • 2008-04-19: Added the need to apply a SQL 2005 post SP2 Hotfix
    • 2008-04-21: DHCP credentials required, SQL SP2 references, ISA not installing on more than 4 cores, and IIS setting for Companyweb.
    • 2008-08-11: Added the note that WSUS v2 should be synchronized prior to WSUS v3 being installed.
    • 2009-08-26: Added the option to allow users to change their password in OWA.
    Philip Elder
    MPECS Inc.
    Microsoft Small Business Specialists

    *All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

    Thursday, 3 April 2008

    SBS - WSUS V3 SP1 Hiccups

    While we have had success with allowing the SP1 of WSUS v3 install on SBS R2 instances, there have been a few hiccups:
    • Make sure to have your scheduled reboot scripts in place when updating remotely.
      • The service pack will break the RWW connection ... serveral times ... most of the time it will not be permanent.
    • You may get a Blue Shield from the SBS WSUS console if the settings were changed during the setup portion of the Service Pack.
    • Make sure the first synchronization finished before refreshing the Blue Shield in the SBS console.
    • If the WSUS based update fails, as we have had one do so far, download and run the Service Pack directly. This seems to work.
    • Make sure there are no consoles open during the WSUS Service Pack application.
    Once finished, you will be good to go.

    Philip Elder
    MPECS Inc.
    Microsoft Small Business Specialists

    *All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

    Tuesday, 5 February 2008

    SBS on dual Xeon E5345 Quad vs. 5130 Dual Core + Symantec EndPoint Memory Costs

    Initially, when we were offered a choice between the Dual Core 5100 series Xeons and the 5300 series Quad Core Xeon processors, we generally aimed for the 5100 series due to cost differences.

    Not too long ago, Intel lowered the 5300 series Quad Core Xeon price to the point where there was very little difference in cost between Dual and Quad Core Xeon processors.

    That is when we started to implement Quad Core 5300 and now 5400 series Xeon processor rigs.

    As a side note: We never supply a dual socket server with only one processor installed. There are a number of very important reasons:

    1. In this day and age of consumer level power house servers the "upgrade path" no longer exists
    2. 18 months from now when the client would otherwise want to "upgrade", one must source a processor with the correct stepping. One cannot just install a Xeon 5150 with stepping B2 with a Xeon 5150 with stepping G0 onto the same server board.
    3. In the case of Tier 1/2, the cost of an extra processor at the time of server build is relatively small compared with plugging the "upgrade" CPU in later. Check with Teir 1/2 and their Post Sale CPU prices. We are generally talking two to three times the initial cost.
    A screen shot of the Xeon 5130 2.00GHz:



    Intel Xeon 5130 2.00GHz Dual Core Series

    And, a screen shot of the Xeon E5345 2.33GHz:

    Intel Xeon E5345 2.33GHz Quad Core Series

    Both parts share the same Front Side Bus speed of 1,333MHz (MT).

    In this case, there is a little difference in the Core speed between the two parts.

    In our experience, the GHz/MHz rates are a limiter on raw speed for events such as booting the server. Generally, the higher the GHz, the faster (incremental) the server will boot. The number of cores on the CPU does not seem to make too much difference one way or another here.

    There is, however, one place we are seeing a marked improvement in performance between the Xeon Dual Core and Xeon Quad Core servers where the Quad Cores triumph: Database driven applications.

    For those of us who work with SBS 2K3 R2 on an ongoing basis, a question for you: How long does the R2 integrated WSUS that has been upgraded to V3 take to come up on an older box? The older the machine, the longer it can take. In some cases, we are talking minutes.

    The following is a screen shot of the Xeon 5130 Cores:

    Intel Xeon 5130 Cores

    The above screen shot was taken during a regular work day for about 20 clients.

    The following is a screen shot of the Xeon E5345 Cores:

    Intel Xeon E5345 Cores

    The above screen shot was taken during a regular work day for about 30 clients.

    On this particular dual Xeon E5345 Quad Core server, the R2 WSUS V3 will come up quite quickly. When the Update Services link is clicked, we can actually watch SQL work across all 8 cores setting things up for the console. Relative to the Xeon 5130 Dual Core, the Quad Core is not quite twice as fast, but there sure is a marked difference.

    Symantec EndPoint Security

    Note the huge step in memory usage on the Xeon E5345 Quad Core based system. The Xeon 5130 Dual Core system has Symantec AntiVirus Enterprise 10.2 and all of the management facilities installed. The memory footprint for this product on the server is relatively minimal.

    The Xeon E5345 has Symantec's new EndPoint product and management system installed. Note that EndPoint is hogging up almost 1.0GB more RAM than the previous version. The new system is almost entirely database driven.

    Here is a screen shot of the Processes:

    Symantec EndPoint Security Memory Usage

    Take note of the number of EndPoint related services running:
    • SMSUtilityService.exe 158MB
    • SemSvc 140MB
    • dbsrv9 80MB
    • SAVFMSETask 58MB
    • SAVFMSESp (x 9) 56MB (~500MB total)
    There are also a number of lesser services tied to EndPoint that are not itemized above.

    For smaller SBS boxes with less than 4GB of RAM, EndPoint will definitely be a struggle to run comfortably along side the standard SBS services.

    Keep this in mind for clients that request a Symantec EndPoint solution on the SBS box and desktops.

    Philip Elder
    MPECS Inc.
    Microsoft Small Business Specialists

    *All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

    Monday, 29 October 2007

    License Advisor is Broken ... Now what?

    Okay, so, we hit the Next button to generate the report and we receive the following:


    A call into Microsoft brought about the following URL: Microsoft Canada Pricing.

    This site gives us all of the relevant Microsoft part numbers for all Microsoft Canada licensing programs and products.

    There does not seem to be a U.S. or U.K. version off the top? Anyone know where the equivalent site is for their respective country?

    Philip Elder
    MPECS Inc.
    Microsoft Small Business Specialists

    *All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

    Monday, 13 August 2007

    System Builder Tip: SBS OEM R2 with W2K3 SP2 SKUs

    While preparing a new SBS install quote we noticed some new SKUs for SBS.

    A couple of part numbers for your OEM SBS installs:
    • Win SBS Premium 2003 R2 English 1Pack DSP OEI CD 1-2CPU 5 Client:
      • T75-01713
    • Win SBS Premium 2003 R2 English 1Pack DSP OEI CD 1-2CPU 5 Client w/WinSvrSP2:
      • T75-02110
    • Win SBS Std 2003 R2 English 1pk DSP OEI CD 1-2CPU 5 Clt SR:
      • T72-01849
    • Win SBS Std 2003 R2 English 1pk DSP OEI CD 1-2CPU 5 Clt w/WinSvrSP2:
      • T72-02193
    Note that OEM versions can now be ordered with Windows Server Service Pack 2 incorporated. Whether they are in Disti's pipe yet is another matter as we don't seem to see stock yet.

    Keep in mind to make sure that all hardware component's firmware is up to date, especially the Intel ProSet NIC drivers. Look for the possibility that adapter teaming will be broken even with a fresh install!

    Philip Elder
    MPECS Inc.
    Microsoft Small Business Specialists

    *All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

    Monday, 9 July 2007

    SBS 2K3 R2 - Setup steps and resources.

    We are running through some setup scenarios on SBS 2K3 Premium R2.

    Here are some resources that come in handy:

    In our experience, to augment the Completing Setup document we do the following when installing SBS 2K3 R2 Premium:

    1. Install the base OS to the primary OS drive formatted leaving 10 GB unused on the drive during setup. All other drives/partitions should be left untouched at this time.
    2. Stop the continuing setup after the reboot by cancelling it.
    3. In between Phase 1 and Phase 2: Install relevant drivers, format the partitions and drives.
    4. Move the Swap File over to the partition created out of the above 10 GB. This partition can be used for the ISA URLCache as well.
    5. Verify all devices are recognized and happy.
    6. Run Phase 2 setup via the Setup icon on the desktop.
    7. We set the MSDE Engine, Users Shared Folders, Client Applications, and Sent Faxes to the same drive/partition.

    8. Finish the install by completing the ToDo tasks.
    9. Install the Premium Technologies with SQL Server 2005 Workgroup Edition followed by ISA 2004 SP1.
    10. Note that during the ISA CEICW one will need to recheck any extra settings at the Web Services Configuration step.
    11. Make sure that the Create Certificate is also left at the setting it chooses.
    12. Install the components and updates from the R2 Technologies CD.
    13. Complete the Post Exchange SP2 Must Dos (previous blog post).
    14. Update the Exchange registry settings for the Greylist problem that Exchange seems to be having: Exchange may not be retrying! (previous blog post)
    15. Install WSS 3.x in side-by-side mode (official SBS blog post on the matter). Why? Because the WSS 3.x and Outlook two way functionality may be required for WSS hosted calendars, or the Recycle Bin may be for those who "accidentally" delete files.
    16. Install WSUS 3.x afterwards (previous blog post on WSUS 3.x install experience).
    17. At the command prompt, run the appropriate osql commands to tame SQL's memory usage (previous blog post explanation).
    18. RipCurl the SBS R2 box for Vista and Office 2007 compatibility (previous blog post).
    In the case of the R2 Tech CD, verify that the Service Packs are still current before installing.

    If newer Service Packs exist, do a bit of searching to verify their compatibility with your SBS installation before installing them. A good example of this is Windows Server 2003 Service Pack 2 as there are lots of caveats on SBS (KB 555912) .

    Our partitioning schemes (previous blog post) come via experience trying to recover multiple partitions on one drive or array. That can be extremely difficult. Sometimes, KISS really works. :D

    UPDATE 2007-09-06: Reversed steps 13 and 15 to set them in the correct order!

    UPDATE 2007-09-07: Added the Exchange registry settings for its seeming difficulty with Greylisting and Tarpitting and the RipCurl step.

    Philip Elder
    MPECS Inc.
    Microsoft Small Business Specialists

    Tuesday, 12 June 2007

    SBS 2K3 R2 - Green Check of Health ... The best it is going to get?

    Recently, one of our SBS 2K3 R2 Premium boxes came up with the following:



    We see the green checks for the Auto-start services, Critical Alerts, and Critical Errors.

    The Yellow Shield for Update Services is pretty much common place now.

    We have updated this particular server to WSUS 3.0 so we have setup the Definition Update automatic allow rule that doesn't break the built-in R2 configured WSUS.

    This means we are not seeing a Red Shield every time Windows Defender received an update. :*Þ

    Given the fact that the Exchange IMF is updated sporadically as an Update Rollup, we almost always see the Yellow Shield because the SBS server is set to "Download and Notify" for updates.

    None of our server installations are set to "Download and Install". That is just plain risky!

    Philip Elder
    MPECS Inc.
    Microsoft Small Business Specialists

    Monday, 21 May 2007

    SBS - POP3 Connector not pulling e-mail

    Every once in a while the POP3 Connector service stops responding.

    To date, we have not found any indication of what failed in the service in the logs, even when the logging level was set to Maximum.

    When troubleshooting the Connector, make sure to have the ISP credentials for one of your users so you can monitor their inbox.

    Restart the service to see if this fixes the problem. Generally it doesn't.

    Consistently, we have to reboot the box.

    As a rule, we see if we can have an MX record with the highest priority for the client's domain pointing to the SBS static IP to mitigate this problem as well as eliminate the 15 minute lag the client experiences when all e-mail comes in via the ISP.

    To complete the MX process, if the ISP is willing, one will need to have the reverse DNS record set for the IP of the SBS box too. This eliminates the possibility that the e-mail will get stopped by spam filters that do a reverse DNS lookup against the sending SMTP server.

    Philip Elder
    MPECS Inc.
    Microsoft Small Business Specialists

    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
    MPECS Inc.
    Microsoft Small Business Specialists

    Monday, 7 May 2007

    SBS 2K3 R2 - WSUS 3.0 install experience with some caveats

    I took to installing WSUS 3.0 on the SBS 2K3 R2 Premium server that was having the most problems with client updates.

    First, one has to make sure to install KB 927891 You receive an access violation error when you try to install an update from Windows Update or from Microsoft Update after you apply hotfix package KB916089a on all of your XP WSUS clients.

    Windows XP KB927891 download link (Note, validation required before download).

    Note, you may experience the following error:

    You do not have permission to update Windows XP.
    You will need to be signed into the workstations as the domain admin, even if your user has local admin rights.

    Once all of your XP clients are up to date, download the WSUS 3.0 files.

    If you are using the R2 integrated version of WSUS 2.0 you will need to leave the settings in their stock form in order for WSUS 3.0 to utilize the R2 integrated features. Essentially, there is no difference in the WSUS setting requirements between versions for R2 integration.

    Download the WSUS Server 3.0 files here. Note the separate files for 32 bit and 64 bit architectures.

    Microsoft has a dedicated document for installing WSUS 3.0 on the various flavours of SBS: Installing Microsoft Windows Server Update Services 3.0 on Windows Small Business Server 2003 (Page link to download Word document).

    Give the above document a read to make sure there are no specific caveats for your relevant server setups.

    As always, there may be caveats for installing or upgrading any software product.

    From the Microsoft TechNet WSUS: Deployment site on 2.0 to 3.0 upgrades:

    Before upgrading from WSUS 2.0 to WSUS 3.0

    You should make sure that your WSUS 2.0 installation is in good working order before upgrading.
    1. Check for recent errors in the event logs, problems with synchronization between downstream servers and upstream servers, or problems with clients not reporting. Make sure that these issues have been resolved before continuing.
    2. You may want to run DBCC CHECKDB to ensure that the WSUS database is correctly indexed. For more information about CHECKDB, see DBCC CHECKDB (http://go.microsoft.com/fwlink/?LinkId=???).
    3. Back up the WSUS database.
    Um, note that the link in number two above points to a search of Microsoft.com. Not too sure why that is the case? Just in case, I ran the search on DBCC CHECKDB.

    Results of a search for "DBCC CHECKDB" from the above Microsoft.com search.

    After the download had completed, I ran the install. It ran without errors and required a reboot. Once the server came back up and running, things were seemingly OK.

    An observation or two about the SBS 2K3 R2 WSUS 3.0 post install/uprade environment:
    • The Reports & Monitoring page and Update Services pages both would no longer come up instantly.
    • The new WSUS db instance (original MSDE is converted to SQL 2K5 internal) runs one core at 100% when bringing up the Update Services page
    • The time to bring up the Update Services page is quite long - expect a long wait on older servers.
    • The new WSUS db instance takes up a large chunk of memory.
    • We received an MMC error on our first trip into the Server Management Console (only happened once):

    The box we installed WSUS 3.0 on is an upper end Pentium D based server. My thought is, given the running of one core at 100% until the Update Services page comes up, older systems will be laboured to run WSUS 3.0. One may receive complaints from clients that things are dogging quite bad on the network if one is managing WSUS during business hours.

    To tame the memory issue one needs to run through the osql commands for the SQL2K5 instance WSUS 3.0 creates (from the command line - assume Enter after each line):
    1. osql -E -S mysbsserver\Microsoft##SSEE
    2. sp_configure 'show advanced options',1
    3. reconfigure with override
    4. go
    5. sp_configure 'max server memory',128
    6. reconfigure with override
    7. go
    8. quit.
    I like to have the Task Manager on the server showing the running processes sorted by memory used when I run the above commands. The SQL instance will literally drop memory before your eyes if it is already using more than your intended maximum memory setting.

    The amount of memory set to the WSUS db instance is arbitrary. Most of our SBS servers have a minimum of 3 GB installed, with the newer ones running 4 GB. Anything less than 3 GB would probably mean a need to curtail memory usage to 96 MB, or even 72 MB depending on server speed and actual physical memory installed. The above 128 MB would be for servers running 2 GB to 3 GB of RAM.

    As always, it is important to assess the impact that the changes made by installing WSUS 3.0 will have on our client's particular SBS infrastructure beforehand! And, your mileage will very. :D

    The WSUS 3.0 Microsoft Site.

    Microsoft TechNet WSUS 3.0 Deployment Introduction.

    Previous blog posts on this subject: Philip Elder
    MPECS Inc.
    Microsoft Small Business Specialists

    Wednesday, 14 March 2007

    SBS, RWW, Fax is Knocking Out RWW Sessions

    I have had a consistent and repeatable issue that has come up lately: if logged in to RWW on a server with the USR 56K USB modem as a fax modem and it receives or sends a fax, it knocks me off the RWW session.

    I am not entirely sure of the reason yet. We have a number of these particular modems out there, and this is the first server, a new R2 installation, that is doing it.

    I will need to look into it further!

    Philip Elder
    MPECS Inc.
    Microsoft Small Business Specialists

    Tuesday, 27 February 2007

    SBS 2K3 R2 - WSUS 0x80070643 for Visual Studio on the Server

    A screen shot of the error:



    Installation Failure: Windows failed to install the following update with error 0x80070643: Visual Studio 2005 Service Pack 1.

    And then, off to the download page here: Microsoft® Visual Studio® 2005 Team Suite Service Pack 1

    Wowzers! A whole 432 MB download! No wonder WSUS choked. Might not be the reason, but it sure could be.

    A little ways down the download page we find:

    The above is a, "just in case" it doesn't work. :D

    Download it, run the install, and all should be good!

    Philip Elder
    MPECS Inc.
    Microsoft Small Business Specialists