Technlogy On the Move : Edwin Joseph

Running Dcpromo to demote and re-promote Small Business Server Products

Edwinjos — Wed, 25 Mar 2009 16:50:56 GMT

Small Business Server 2003 and Small Business Server 2008 have to be Primary domain controller in the domain Small Business Server product are an integrated product with Exchange SharePoint, and IIS installed on the same server along with Active directory
So whatever reason it might be we should not Dcpromo down Small Business Server as this will break the integration of the various installed application on Small Business Server
Hence Dcpromo down and re-promoting the same Small Business Server is not supported
If Dcpromo down has been run on the Small Business Server the only supported mean to promote it back as domain controller is to rebuild the server starting fresh
If you have and additional domain controller in the domain which is always recommended we could follow http://support.microsoft.com/?id=884453 to join Small Business Server 2003 to an existing active directory domain.
For Small Business Server 2008 http://technet.microsoft.com/en-us/library/cc546034.aspx should be followed

Browse Remote Web Workplace from Windows XP SP3 machine

Edwinjos — Fri, 07 Nov 2008 19:58:00 GMT

History:

The Microsoft Terminal Services Client ActiveX control (also known as Microsoft RDP Client Control) Is ActiveX is component offered by the server This is a downloadable ActiveX control provides nearly the same functionality as the full Terminal Services Client, but is designed to deliver this functionality over the Web. The ActiveX control does not come installed as part of any Windows client system. Instead, clients obtain the control from web servers that offer terminal services. The configuration process that enables an IIS server to provide terminal services involves installing on the server a file containing the control. The server then delivers this file to any client system that needs it, and the client installs the control

When trying to browse remote web workplace hosted on a Small business Server 2008 we get the following error

VBScript: Remote Desktop Connection

The wizard cannot configure Remote Desktop Connection settings. Make sure that the client version of Remote Desktop Protocol (RDP) 6.0 or later is installed on this computer.

When we verify the version of mstsc .exe 6.0.6001.18000 however when we check the add-ons currently loaded in Internet Explorer 7 it show

Microsoft RDP client Control ActiveX control (Msrdp.ocx)

This is terminal services client add-on for Remote Desktop Protocol 5.0 as per the above mention error message we need Remote Desktop Protocol (RDP) 6.0 or later when we install Windows XP Service Pack 3 (SP3) The Microsoft Terminal Services Client ActiveX control is already includes this ActiveX control and installs it by using the Mstscax.dll file. By default, this ActiveX control is disabled in Windows XP Service Pack 3 (SP3).

if we disable Microsoft RDP client Control ActiveX control (Msrdp.ocx) add-on we get the error as follows:

VBScript: Remote Desktop Connection

The Microsoft Terminal Services Client ActiveX control (also known as Microsoft RDP Client Control) is either not available, or is not enabled. For more information about installing and enabling this ActiveX control, see the Microsoft TechNet Web site (http://go.microsoft.com/fwlink/?LinkId=103719).

do backup the favorites in Internet explorer

Reset the Internet Explorer Settings to defaults

Regsvr32 Mstscax.dll located in %Windir% \system32

Close all open all instances of Internet Explorer

Try browsing Remote Web Workplace now The Microsoft Terminal Services Client ActiveX control should be offered by the server install this ActiveX

Troubleshooting Event id 1006 Userenv Error On Client Workstation

Edwinjos — Tue, 19 Feb 2008 19:35:00 GMT

Problem Descritpion

Event Source: Userenv

Event Category: None

Event ID: 1006

Date: 2/14/2008

Time: 12:07:04 PM

User: njfpc\LD

Computer: LAPTOP06

Description:

Windows cannot bind to <Domain name>domain. (Invalid Credentials). Group Policy processing aborted.

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

AND

In User Env Logs

USERENV(374.2bc) 12:07:04:687 GetGPOInfo: ********************************

USERENV(374.2bc) 12:07:04:687 GetGPOInfo: Entering...

USERENV(374.2bc) 12:07:04:687 GetGPOInfo: Server connection established.

USERENV(374.2bc) 12:07:04:703 GetGPOInfo: ldap_bind_s failed with = <49>

USERENV(374.2bc) 12:07:04:703 GetGPOInfo: Leaving with 0

USERENV(374.2bc) 12:07:04:703 GetGPOInfo: ********************************

Troubleshooting

The error message states its unable to bind to domain name so

1) we need to verify that we are able to access Share on the SBS specially Sysvol and netlogon share from the client

2) the time Difference between the Server and Clients is plus minus 5 minutes not more

3)The Server is advertising itself as a Time Server In Dcdiag

4) Make sure the Binding order of the Network Interface cards is Correct

5) Start -> Run -> "control keymgr.dll" remove any entries that you have for cached Domain passwords

6) Gpupdate /force log off and relogin

happens most of the time due to invalid cache domain password being used for authentication mostly when it come to laptops

Reference Article :

http://support.microsoft.com/kb/221833