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 firstname.lastname@example.org –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
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:
- Disable Cached Mode in Outlook
- Connect to the start Outlook and connect to the Exchange Server
- 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
For all you people who are getting ALOT of email or just want to stay on top. Take a look at this “Getting things done” inspired email management system for Outlook.
Today I came across a WSUS problem…
After having some problems with the install of WSUS 3.0 SP1 i was not able to uninstall it and hence not reinstall it. I found this article on the WSUS Support team Blog Site.
On the source server:
netsh aaaa show config > file.txt
On the target server
netsh exec file.txt
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.
Deletes files no longer needed.
3. WSUS Cleanup Script
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.
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:
When connected, type the following two commands:
Alternatively, you can type the following two commands:
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.
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.
- Create a folder for the patches (example: C:Program FilesMicrosoft Dynamics CRMServercrmpatches)
- Create a virtual directory in the CRM website (or on another website) pointing to the folder created in paragraph 1.
- Copy the patch to the new folder.
- 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)
- 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>
Save the file as configtool.xml
- Start the configtool from command prompt
This imports the patch into the CRMConfig db
- Run the following reg file on all client or roll it out using a GPO.
Windows Registry Editor Version 5.00
The problem is that the ActiveX controller does not work in Windows Vista… Here is a solution