SBS RWW ActiveX Control Error

A problem discovered by another technician for a client which  points to a possible problem with clients which use RWW to connect to their desktop computer at the office who are running Windows XP SP-3 with IE8 installed. The symptom is that when they click to see a list of computers that they can connect to, they see:

“This portion of the Remote Web Workplace requires the Microsoft
Remote Desktop ActiveX Control. Your browser’s security settings may
be preventing you from downloading ActiveX controls. Adjust these
settings and try to connect again.”

Be sure to check the following:

  • IE Compatibility Mode is enabled for the RWW site
  • The site is on the “trusted site” list
  • From the command line, type “regsvr32 mstscax.dll” to re-register the control

Microsoft SBS – RWW on XP SP-3 with IE8 Installed

Wow, what a short title full of abbreviations! A problem discovered by another technician points to a possible problem with clients which use RWW to connect to their desktop computer at the office who are running Windows XP SP-3 with IE8 installed. The symptom is that when they click to see a list of computers that they can connect to, they see: 

This portion of the Remote Web Workplace requires the Microsoft Remote Desktop ActiveX Control. Your browser’s security settings may be preventing you from downloading ActiveX controls. Adjust these settings and try to connect again.
 

Be sure to check the following: 

  • IE Compatibility Mode is enabled for the RWW site
  • The site is on the “trusted site” list

 

mstscax.dll” to re-register the controlregsvr32From the command line, type ”

 

 

Microsoft SBS Wizard Troubleshooting

3d human with a red exclamation markToday I have resolved my fourth SBS Wizard related problem this year. The symptoms are the same on both SBS 2003 and SBS 2008 – when attempting to use the Wizards to create a user or computer, the wizard works all the way until the last step and then fails with an error.

The problem in all four cases this year have been because someone treated an SBS server like a Windows Standard Server. And the reality is that while it is based upon standard server, it really is not. There have been major tweaks and adjustments to permit it to work the way it does. Among them is various restrictions on changes to Active Directory. Basically, unless you understand exactly how the SBS Wizards leverage Active Directory, it is best not to do anything through the standard Active Director Users and Computers console. The Wizards require that users, computer and other data are placed in very specific Organization Units, with very specific names. Renaming OUs or moving users into a more “logical” place will prevent the wizards from working properly.

The people who get themselves into too much trouble are often IT consultants who think they know better – but really don’t. The reason is that a newbie administrator will actually read the documentation that comes with SBS and/or pickup a great reference book, which all say the same thing — use the wizards for absolutely everything, don’t make any changes to Active Directory outside of a wizard. The only exception being would be documentation which specifically takes SBS into account. A Microsoft Technet page will specifically call out that it works with SBS; if it just mentions Standard Server, beware! Remember that SBS is made for oranizations of 75 users or less, and in these environments, rarely will you need a complex OU scheme.

In all four cases this year, it has been because someone has renamed or deleted the default SBS OUs which are created automatically. A quick rename of the OUs back to what they were origionally named, will resolve your problems. That’s it, no big changes, registry adjustments, etc. Simply put the OUs back to where they were automatically created and you should be all set.

Remember, SBS 2003/2008 is not Standard Server, nor is it Exchange Standard — it is a (for lack of better terms) hacked version of Server Standard and Exchange Standard – they are ment to be managed nearly 100% by the wizard and SBS consoles.

Shared Fax Server on Windows Server 2003

3d human try to turn the pageEver since I began using Microsoft Small Business Server 2000, I was thrilled with all of the features included which were not found anywhere else by Microsoft. Many of the useful features required third-party add on tools. One such tool was the shared fax server.

Beginning with Microsoft Windows Server 2003, a shared fax server became a built in feature. However documentation on how to implement this new feature is sparse at best. This documentation is based on a Windows 2003 Server (all editions except Web), and Windows XP for your client. Continue reading “Shared Fax Server on Windows Server 2003”

Powered by WordPress.com.

Up ↑