RES Workspace manager Express license not activating + How to solve it

When installing RES workspacemanager 2011 RS2 i found out that we couldn't register the Express Edition of this software.

But Express Edition has unlimited users and the Evaluation version just 25 seats.

The Query: "select * from tblSettings where lngClassID = 38" run without the quotes. It wil give you 9 results. Within the results probably there's the one who's causing the failure.

run now Query: "delete from tblSettings where lngClassID = 38" again without the quotes. This deletes the faulty registered keys.

Then start the RES Workspace Manager Console, set the licensing from Gold to Express and then register the Express edition. The activation will now succeed like the last 2 screens.

When you run the License Wizard you could get stuck in the following screen:

Error mentioned above when trying to activate

The Evalution license in RES

Results of the query on the Database

License registration succeeded

Unlimited licenses now available

Install WSUS on 2008 R2 SP1

WSUS 3.0 SP2 Configuration Steps

After installing WSUS 3.0 SP2 on windows server 2008 the configuration wizard will be launched automatically.

1- In the Before you begin screen click Next.



2- In the Microsoft update improve program click Next.



3- In choose upstream server select synchronize from Microsoft update and click Next.



4- In specify proxy server screen type your proxy settings (optional if you have a proxy server) and click Next.



5- In connect to upstream server screen click start connecting button.



6- After successful connection click Next.



7- In choose language screen select English (or any other languages) and click Next.



8- In choose product screen select the products that you have to download it's updates and click Next.



9- In choose classifications select the classifications of updates to download and click Next.



10 - In Set sync schedule screen select Synchronous Automatically and specify suitable time for you and synchronize rate and click Next.



11- In Finished screen click Next.



12- In What's Next screen click Finish.

Get rid of annoying welcome screen IE8

Using Group Policy Editor
If your version of Windows includes the Group Policy Editor, you can modify this setting using these steps:

1. Launch the Group Policy Editor (gpedit.msc)
2. Expand the following branch:

Computer Configuration | Administrative Templates | Windows Components | Internet Explorer

3. Double-click Prevent performance of First Run Customize Settings

4. Set it to Enabled, and select Go directly to home page.
5. Click Apply, close the dialog and exit the Group Policy Editor.

Error Exchange 2003: One or more users currently use a mailbox store on this server

Ever tried to remove Exchange 2003 after you moved all mailboxes to Exchange 2010 SP1. And got this annoying error that was telling you that a user still has a mailbox in the information store on the exchange server that you were trying to remove??

Read on and find out how to discover this orphan user.

Method 1 (Active Directory Users and Computers):
- Right-click the domain container, and then click Find
- Select the Exchange tab
- Check the "Show only Exchange recipients" check box
- Check the "Users with Exchange mailbox" check box
- Click Find Now
- On the View menu, click Choose Columns
- Select "Exchange Home Server" in the Columns available list and click Add
- Click OK
- Click the Exchange Home Server column to sort the results

The server that appears in this column is the same value that appears in the msExchHomeServerName attribute.

Method 2 (Active Directory Users and Computers):
- Right-click the domain container, and then click Find
- Select the Advanced tab
- Select User from the Field button
- From the list of attributes displayed, choose Exchange Home Server
- Set the Condition field to Ends With
- Enter the Exchange server name into the Value field
- Click Add
- Click the Find

Method 3 (ADSIEdit.msc from Support Tools): *
- Expand server.domain.com
- Expand CN=Configuration,DC=domain,DC=com
- Expand CN=Services
- Expand CN=Microsoft Exchange
- Expand CN=OrganizationName
- Expand CN=Administrative Groups
- Expand CN=AdministrativeGroupName
- Expand CN=Servers
- Expand CN=ServerName
- Expand CN=Information Store
- Expand CN=StorageGroupName
- Right-click CN=Mailbox Store (ServerName) and select Properties
- In the Select a property to view list click homeMDBBL

* Warning: I'm not liable for damage to your Domain or Exchange environment when using this blog. It's on your own risk to use Adsiedit, or other advises mentioned above.

Only experienced users should use this powerfull tool. Others just use the first two steps.

Symplify Exchange OWA url 2010 SP1 / SP2

Users want a simple access to the webmail. So i decided to edit the settings of the url. So that users can just type in the address bar webmail.contoso.com instead of https://webmail.contoso.com/owa or /exchange. Just redo the steps below when you installed SP2. The installation has done a reset to the default Exchange settings.

Just select the default website in the IIS. Go to "HTTP Redirect" and edit the default url.

When you set the redirect settings on the "Default Website" undo this settings on the Vdir's:

• aspnet_client
• Autodiscover
• ecp
• EWS
• Microsoft-Server-ActiveSync
• OAB
• PowerShell
• Public
• Rpc

Also for the SSL settings, when edited on the "Default Website" it's inherited by the other Vdir's. So undo it manually.

• Autodiscover
• ecp
• EWS
• Microsoft-Server-ActiveSync
• OAB
• owa
• Public
• Rpc

When this is done, open a elevated commandprompt and type "iisreset" (without the quotations ofcourse)

NOTE: when SP2 is installed, just undo the SSL settings otherwise the redirection won't work!!

When the settings are done and you want to reset the IIS and /noforce won't work. Just use iisreset, later on the site is working.

When you install Exchange 2010 SP1, reboot the server afterwards. Later on install the latest Rollup. Latest is version 6.

http://www.microsoft.com/download/en/details.aspx?id=27849

If you have a error in your Webapp now, you have forgotten to remove the Redirection on the public Vdir.