June 2008 Archives

Had a case open with Microsoft, took several weeks to come to a conclusion actually. But, felt this might help someone, so I've posted the result.

Subjective:
************
When you click on "Process Expired items now" in your production environment, the button becomes unusable (grayed out) and does not become usable until you remove the Timer Job Definition associated with the "Process Expired items now" button press.

Case Resolution Agreement:
*************************
This case would be considered resolved and ready to close when the "Process Expired items now" button in your production environment becomes available after pressing it without having to delete the "Expiration Policy (manually initiated)" Timer Job.

Objective:
***********
MOSS 2007
Windows 2003

Assessment:
*************
I observed the behavior you were seeing in your production and your QA environments. In QA, the button works as expected, but in production the button remains grayed out after clicking it.

I did some research on this issue and found that we needed to "reactivate" the Records Management feature using the stsadm command below.

stsadm -o activatefeature -filename recordsmanagement\feature.xml -force

We successfully ran the above command on the production SharePoint Server, and tested the "Process Expired items now" button. This time, the button became available again on its own, without having to manually delete the "Expiration Policy (manually initiated)" Timer Job.

You'll need your organizational forms library recreated (you probably didn't replicate it during your Exchange 2003 to 2007 migration).

How to create an Organizational Forms Library in Exchange 2007 - http://support.microsoft.com/kb/933358

Looking to run VMware server in your environment and want to have 64bit guests? This keeps cropping up so it was time to catalog the information a little bit so I don't have to keep looking for it.

VMware knowledge base regarding having 64bit support:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1901

A nice breakdown of the issue and how to check your existing server if you've already bought it :)
http://www.petri.co.il/virtual_run_a_64_bit_guest_operating_system_in_vmware.htm

Ran into this tonight and after hours of scouring (and Microsoft's own KB not helping me find the answer via their search ... yeesh!) Google, etc., finally found the solution to the issue I had at a client site.

Default printer cannot be set

Microsoft KB : 933996- A user who is logged on to a Windows Server 2003-based Terminal Server cannot configure a printer as the default printer

Link: http://support.microsoft.com/kb/933996

Well, this was a frustrating experience, as I was trying to make Outlook Anywhere work with a single cert, only realizing later that I needed a wildcard cert, which I didn't have. Anyways, got it licked with the following information that I'm bookmarking so I don't have to chase it later. The first short blog was definately the most useful in sorting out where I was going wrong.

http://msexchangeteam.com/archive/2007/09/21/447067.aspx - in particular, this has the pro/con list defined for the various SSL options that exist, though it discusses a new SRV record option, which is supported with several requirements, such as particular hotfixes.

AutoDiscover WhitePaper

SRV Record details


Well, this is getting more and more interesting...

Nevermind the SNP feature pack in SP2 for Windows Server 2003 sucks and that this patch helps reverse it...

http://support.microsoft.com/?kbid=948496

But better still, after applying the patch (and in general, these symptoms occur), applying a reboot to a server that has just been patched, using a Remote Desktop connection (RDP), the server goes into a state where:

  • connectivity is slow
  • RDP is no longer available
  • it appears it has shutdown but doesn't come back up

The harsh reality is that its only partly down, and the reboot has not occurred properly. The good news, assuming you have at least one other Windows machine on the same network that you can access remotely, is that you can use the shutdown.exe /i command to launch the remote shutdown command and push a reboot to the server. After applying http://support.microsoft.com/?kbid=948496, assuming you did during this issue, reboots following it will be better.

Yahoo!

This fella blogged this too... so its good to know I'm not alone.

http://theessentialexchange.com/blogs/michael/archive/2008/02/14/windows-2003-sbs-2003-restart-problems.aspx