I Found a really usefull post which shows how to fix Just this issue!

Option #1:Repair Damaged Certificate (Windows Server 2003/2008)

1. Open MMC and add the Certificate Snap-In for the Local Computer account.
2. Double-Click on the recently imported certificate
3. Select the Details tab.
4. Click on the Serial Number field and copy that string
5. Open up a command prompt session. (cmd.exe aka DOS Prompt)
6. Type: certutil -repairstore my “SerialNumber” (SerialNumber is that which was copied down in step 4.)
7. After running the above command, go back to the MMC and Right-Click Certificates and select Refresh (or hit F5 in the MMC)
8. Double-Click on the problem certificate. At the bottom of this window (General tab) it should state: “You have a private key that corresponds to this certificate.“

30 seconds later – Legend!

Just keep in mind, SBS likes to have any certificates with a subordinate authority also have their certificates listed in the MMC -> Certificates -> Server -> Trusted Subordinate Authorities.

1. Backup C:\Program Files\Trend Micro\Officescan\PCCSRV\Private\AuthorStore\TrendAuthDef.xml

2. Open the C:\Program Files\Trend Micro\Officescan\PCCSRV\Private\AuthorStore\TrendAuthDef.xml file in edition.

3. Replace the Root information at the bottom of the file as shown below:

<AppUsers Maxsid=”2″>

        <AppUser Domain=”" Email=”" Fullname=”Administrator account created during installation” Sid=”S-1-9-1-2″ Pwd=”!CRYPT!523F7DC2E525044E2800FCDEA7E5D78B70C0A4165387060525E3EE66D5D2D2F460EA361E712B5F871FD473C7A6C” WinUser=”0″ Enabled=”true”/></AppUsers>

Note: Replace only the portion for the root. If there are other accounts showing please do not delete them.

4. Restart the OfficeScan Master Service.

5. Log in as root and use “trendmicro” as the password.

6. Change the root password to something more secure by going to Administration > User Accounts.

7. Click on the root account to type in the new password.

Problem Solvered :-)

After using Outlook 2010 beta for the past 6 months, I definitely recommend upgrading. Just like with Windows 7, when you are forced to use an older version of Outlook you really miss all the new shortcuts and features.

While not officially supported by Microsoft, there is an excellent modification that The Missing Remote has published. A simple batch file installs a different DLL for Terminal services that allows the console to remain logged on while up to 2 other users log into a separate RDP session.

Now I can do any management and monitoring or changes necessary without having to submit a “TV-Outage Request”. :-D Very cool.

Now you can modify the memory and processor, log files, etc.

Step 1. Access List

NOTE: You can specify IP addresses or traffic types here.

ip access-list extended <VOICE>
 permit udp any any range 16384 32767
ip access-list extended <VOICE-CONTROL>
 remark Match VoIP Control Traffic
 remark SIP
 permit tcp any any range 5060 5061
 permit udp any any range 5060 5061
 remark SCCP
 permit tcp any any range 2000 2002
 remark H323 Fast Start
 permit tcp any any eq 1720
 remark H323 Slow Start
 permit tcp any any range 11000 11999
 remark MGCP
 permit udp any any eq 2427

Step 2.  Class Map

NOTE: The ‘match-all’ or ‘match-any’ commands are like using AND/ OR for the access lists specified.

class-map match-all <VOICE-CONTROL>
 match access-group name <VOICE-CONTROL>
class-map match-any <VOICE>
 match access-group name <VOICE>
 match ip dscp ef
 match ip precedence 5

Step 3.  Policy Map

NOTE: The ‘priority’ command is the same as bandwidth but gives this traffic first access to bandwidth. You can only specify this command once.

policy-map <VOICEWAN>
 class <VOICE>
    priority <number-kbit>
 class <VOICE-CONTROL>
    bandwidth <number-kbit>
 class class-default
    fair-queue

Step 4. Interface Configuration

interface <outside_interface>
 bandwidth <number-kbit>
 bandwidth receive <number-kbit>
 service-policy output <VOICEWAN>

What’s so hard about that?

Mobile phones are a little different, for one they use HTTPS to sync data. Secondly, data traffic is generally more expensive so when there is no new data, you want the phone to send as few data packets possible. When you create a ‘Publish Outlook Anywhere’ rule with ISA 2006, this automatically configures the firewall to let TCP sessions stay open for up to 30 min without seeing any traffic. Meaning that when there is no new email, the phone will send a single data packet every 30 min.

Unfortunately if your running any other type of firewall (ASA, PIX, NetGear, ISA 2004, etc.) you will need to manually configure this setting. By default, most firewalls will forcefully close a session that is idle for 5 min for security reasons AND on most SOHO firewall’s you can’t change this setting.

Moral of this story, if you use ActiveSync with push enabled on client mobile phones and don’t use ISA 2006 as your Internet firewall, you will likely have sessions from mobile devices disconnected causing Error 3033 on the Exchange Server Event Log. There is a Microsoft KB Article that shows simple change you can make to the ActiveSync web.config file to specify the maximum TCP session limit for your firewall to 5 min. eg,

<add key="MinHeartbeatInterval" value="60"></add>
<add key="MaxHeartbeatInterval" value="300"></add>

On a serious note though, Alan and Lilia did an awesome presentation at TechEd and I’m sure this site will show the same level of awesome-ness. Rock on Al.

Good news! Office 2010 fixes the Office 2007 issue, where-by you need to resort to implementing fixes yourself, to get Quick Access Toolbar and the new customisable Ribbon to roam between computers. You’ll have to remember to enable this option yourself though – create a Setup customisation with the Office Customisation Tool and enable the following option:

Features – Modify user settings – Microsoft Office 2010 System – Global Options – Customize – Allow roaming of all user customisations

He also points out the MS Knowledge Base article to enable roaming for Office 2007 settings as well.

Thanks Parky