Exchange Server Blog: Room Mailbox Scripts Exchange Server 2007

Today i was looking for some good scripts for handling room mailboxes. I found these:


new-Mailbox -alias “Meeting Room” -database “Mailbox Database” -name “Meeting-Room” -resourcetype room –userPrincipalName room-meetingroom@exch.local –OU “Resource Mailboxes/Company”

Creates a new Room Mailbox

Set-MailboxCalendarSettings MeetingRoomAlias -AutomateProcessing:AutoAccept

Enables Auto Accept

Set-MailboxCalendarSettings MeetingRoomAlias – AddAdditionalResponse $True
Set-MailboxCalendarSettings MeetingRoomAlias – Additional Response “This is the custom Response”

Sets alternate decline response.


Exchange Server Blog: Room Mailbox Scripts Exchange Server 2007

Enable Search folders in Outlook Web Access

I have started using this method for organizing my mail and since it is very reliant on search folders I wanted to be able to access my search folders from Outlook Web Access.

To get this working you need to do the following:


  1. Disable Cached Mode in Outlook
  2. Connect to the start Outlook and connect to the Exchange Server
  3. Refresh your Search Folders


If you re-enable Cached Mode it will still work but you will not be able to add new Search Folders


WSUS Cleanup Tips

Here are some tips if you have an ever growing wsuscontent directory and you are running out of space:

1. Decline superseded update

You can delete superseded updates IF you have approved the superseding updates. If you decline the superseded updates the “Server Cleanup Wizard” will delete them and you will get more free disk space.

2. WsusDebugTool.exe

WsusDebugTool.exe /Tool:PurgeUnneededFiles

Deletes files no longer needed.

3. WSUS Cleanup Script

Citrix Metaframe having problems with Windows Server 2000 SP4 Rollup Fix 1

The other day I ran into a problem with an old Windows 2000 Citrix Server which suddenly stopped accepting some connections. The problem turned out to be that they recently updated the server with Rollup Fix 1 (from 2005). It seems that there is a problem with RO1 together with Citrix. The fix needs to be manually downloaded from MS.


Finding out version and edition of a Microsoft SQL Server

The other day at a customers I needed to find out the version and edition of an installed SQL server… Here is the solution:

Connect to an instance of SQL Server by using the following sqlcmd command:

sqlcmd -S ServerInstance

Where Server is the name of the computer and Instance is the name of the instance you want to check. If you have used the default named instance during setup, specify the instance as “SQLExpress”.

To identify the server name and instance name, type the following command:

select @@servername

When connected, type the following two commands:

select @@version

Alternatively, you can type the following two commands:

select serverproperty(‘edition’)

The sqlcmd tool displays the version information. If the last line of information includes “Express Edition,” the instance to which you are connecting is running SQL Server Express.

Thanks Anders…


Microsoft CRM 4.0 and Automatic Patching

This is a short description of how to rollout Rollup Fix 1 for Microsoft CRM using the automatic update feature in Microsoft CRM 4.0.


  1. Create a folder for the patches (example: C:Program FilesMicrosoft Dynamics CRMServercrmpatches)
  2. Create a virtual directory in the CRM website (or on another website) pointing to the folder created in paragraph 1.
  3. Copy the patch to the new folder.
  4. Get the patchid for the patch. To do this extract it to a temporary folder using: CRMv4.0-KB952858-i386-Client-INTL.exe /x. Open the config.xml in the temporary folder and copy the patchid (eg 9D28D100-595D-4CC4-AE00-6A90913B968D)
  5. Create an xml file that looks like this:

    <?xml version=”1.0″ encoding=”utf-8″?>
          <Title>Microosft CRM 4.0 Rollup 1 Sw</Title>
          <Description>This is a rollupfix for Microsoft CRM 4.0 Swedish</Description>
          <ClientType>OutlookLaptop, OutlookDesktop</ClientType>

    Save the file as configtool.xml

  6. Start the configtool from command prompt

    [Path]Microsoft.Crm.Tools.ClientPatchConfigurator.exe [Path]configtool.xml

    This imports the patch into the CRMConfig db

  7. Run the following reg file on all client or roll it out using a GPO.
  8. Windows Registry Editor Version 5.00