• Main
  • Blog
  • Who We Are
    • Jeremy Anderson
    • Amy Babinchak
    • Philip Elder
    • Cliff Galiher
    • Chris Matthews
    • Eriq Neale
    • Edwin Sarmiento
    • David Shackelford
  • HelpDesk
  • FAQ
  • Datto
  • SMBKitchen Project
    • SMBKitchen Crew

Archive for SBS 2003

Sep
8

Manually uninstalling the Worry-Free Remote Manager (WFRM) 1.0 / 2.0 Agent

by steve

When upgrading to WFBS and WFBSA 6.x from previous versions of Trend Micro WFBS and CSM for SMB, I've had multiple times where the Worry-Free Remote Manager Agent install fails and gives the following pop-up error:

Unable to load Library C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{43F8CF32-15B7-44DD-A01D-A3372DD2856E}\zlib1.dll.

If you run across this, Trend has a great KB that will walk you through doing a manual removal. If you keep the GUID in your Worry Free Remote Management Console, then you can do a copy and paste into the new install of the agent and you'll be set.

If you don't feel like clicking through to the KB, here's a copy of it as of 9/8/2010:

Manually uninstalling the Worry-Free Remote Manager (WFRM) 1.0 / 2.0 Agent 
 
Solution ID: EN-1035023
Product: Client Server Messaging Security for SMB - 3.5, 3.6; Client Server Security for SMB - 3.5, 3.6; Worry-Free Remote Manager - 1.0
Operating System: Windows Server 2003 Standard Edition - SP1; Windows 2000 Server - SP4
Published: 4/3/2009 1:00 AM 
 
 
Solution: Public

--------------------------------------------------------------------------------

Please do the following:
 
     
1. Stop the Trend Micro Worry-Free Remote Manager Agent service.

   a. Click Start > Run.
        
   b. Type "cmd" on the command line and then press the Enter key.
        
      Run this command:   
      net stop Trend Micro Worry-Free Remote Manager Agent
 
     
2. Remove the Trend Micro Worry-Free Remote Manager Agent service.
        
   a. On the command line, use the change directory (cd) command to go to the WFRM Agent directory.
        
   b. Run this command:
        
      TMICAgent -u
     
3. Remove the program files.
     
   Delete [agent install directory] – WFRMAgentForCSM
     
4. Open the Registry Editor (regedit.exe) and then remove these registry keys:
     
   Important:Always create a backup before modifying the registry. Incorrect registry changes may cause serious issues. Should this occur, restore it by referring to the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.
     
   •  HKEY_OCAL_MACHINE\SOFTWARE\TrendMicro\TMIC4CSM\Agent\...
        
   •  HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\ 23FC8F347B51DD440AD13A73D13A73D22D58E6
        
   •  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\23FC8F347B51DD440AD13A73D13A73D22D58E6
        
   •  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{43F8CF32-15B7-44DD-A01D-A3372DD2856E}
        
   •  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\InstallShield Uninstall Information\{43F8CF32-15B7-44DD-A01D-A3372DD2856E}
        
   •  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\InstallShield_\{43F8CF32-15B7-44DD-A01D-A3372DD2856E}
     
5. Remove the WFRM Agent shortcut from the Start menu.
        
   a. On the desktop, click My Computer.
   b. Change the current directory to ..\Documents and Settings\All Users\Start Menu\Programs.
   c. Delete the Worry-Free Remote Manager Agent folder.

Categories : SBS 2003, SBS 2008
Apr
15

SBS 2003 Monitoring and Update Services Node Failing on April 14

by Third Tier

Post to Twitter Post to Facebook Post to StumbleUpon

Many SBS 2003 R2 servers experienced an unusual interruption in the daily monitoring reports and system administrators also noted that the Update Services node in the Server Management Console failed to display correctly starting Wednesday, April 14, 2010. The Official SBS Blog has a post explaining the issue and a workaround/resolution for the problem at http://blogs.technet.com/sbs/archive/2010/04/14/windows-sbs-2003-update-services-gives-error-the-element-already-exists-in-the-collection.aspx.

If you’ve been experiencing this issue with your SBS 2003 R2 servers, follow the instructions in the SBS Blog to address the problem.

0 Categories : SBS 2003
Jan
11

Microsoft Product Support Lifecycle for SBS 2003

by steve

Having a hard time figuring out the Microsoft Product Support Lifecycle (also referred to as the end of life date) for SBS 2003? Selecting one of the Windows Small Business Server 2003 options from http://support.microsoft.com/gp/lifeselectserv makes me feel like I need a flowchart to decipher the notes.

For the easy one, SBS 2003 WITHOUT SBS SP1 went end of life on 7/10/2007. If you still haven't installed SBS 2003 SP1, do it now!

SBS 2003 SP1 falls under the following rules:

Support ends 24 months after the next service pack releases or at the end of the product's support lifecycle, whichever comes first. For more information, please see the service pack policy at http://support.microsoft.com/lifecycle/#ServicePackSupport .


SBS 2003 R2 Premium and Standard fall under these rules:

The support date for this product package is determined by its individual component product’s respective support lifecycles. Please review the individual component product’s support lifecycle to determine its length of support.

 

Are you wondering when you are going to have time to look all the products up and check 'em out for their individual dates? I was. Thankfully, Lennart Wistrand with the SBS team has done some of the back-end work for us to make it simpler. Use Lennart's notes below (valid as of 1/11/2009) to help you figure out the end date for your version of SBS03:


Important dates to keep in mind for SBS 2003 when reading its lifecycle.

• http://support.microsoft.com/lifecycle/?p1=1773: Exchange Server 2003’s EOL date is April 8, 2014.
• http://support.microsoft.com/lifecycle/?p1=7022: Windows SharePoint Services 2.0 is July 9, 2013.
• http://support.microsoft.com/lifecycle/?p1=2852: SQL Server 2000 goes out of support on April 9, 2013.

Customers would need to be on ISA Server 2004 and WSUS 3.0 for the server to be supported up until these dates. For SBS2K3 R2 customers, the SQL date is later than the Exchange date.

Thank you Lennart!!

Categories : SBS 2003, Steve
Dec
17

BPOS Sync Tool does not migrate passwords

by steve

Had this question come up today, so thought I'd drop a quick post on it. The Directory Synchronization tool used with Microsoft's Online Services does a one-way sync from your Active Directory up to the BPOS servers, and does not migrate passwords. You have to do those manually, and if you change a password in your local AD, it must be updated manually on the BPOS side.

See the Microsoft Online Services "About Directory Synchronization" page for the official wording on it.

Categories : SBS 2003, SBS 2008, Steve

Search

Support

Third Tier provides advanced support services to IT Professionals. Learn about what we do at http://www.thirdtier.net or click on the support icon below to chat with one of our support representatives.

Live Chat Software by Kayako
Third Tier
Copyright © 2013 All Rights Reserved
iThemes Builder by iThemes
Powered by WordPress