Great table on the features of ActiveSync and what each client (device) can do, – Wikipedia
For some reason when using Outlook, all of the saved names/email addresses in the Outlook cache (.nk2) file was not being read by Outlook 2010. When looking at the .nk2 file in userAppDataRoamingMicrosoftOutlook it had been renamed to Outlook.nk2.old. When I renamed the .nk2 file back to Outlook.nk2 file, Outlook still would not use the autocomplete file. When having no .nk2 file Outlook didn’t create a .nk2 file either….weird. So, I found a way to import the .nk2 file in outlook: Close Outlook, go to the run window and type outlook.exe /importnk2
Microsoft Support KB – link
At some time you may need to change the default location of the Trend Micro Client/Server Security Agent on a desktop/server. In our case the server was very low on disk space on the C: drive, but the default install when executing \servernameofcscanautopccp.exe would go to the C: drive.
- Open the ofcscan.ini file, and go all the way down to the bottom of the file
- Change the path on the line “WinNT_InstallPath=$ProgramFilesTrend MicroClient Server Security Agent”
- Save the file and run autopccp.exe and it will go to the new path that you have saved
When users delete items from folders, outlook doesn’t seem to refresh the item list. If you try and delete the item again, outlook throws an “unknown error” message. If you delete an item and then navigate away from a folder or even use the navigation pane to display the same folder, the item list will refresh and remove the deleted message.
The issue is “The basic issue is that Outlook 2003 support UDP and polling notifications. Exchange 2007 supports UDP, polling and Async notifications. Exchange 2010 only supports polling and Async notifications. This means when Outlook 2003 move from Exchange 2007 to Exchange 2010, Outlook clients will fall back to polling which by default only gets notifications every 30secs-1min. This means any change won’t show up immediately.
UDP notification support was removed from Exchange 2010. As a result, Outlook 2003 can only use polling notifications in online mode, which are still supported by RPC Client Access. This will result in a slight delay in updates to item status (30 seconds on average up to a 1 minute delay) when changes are made to items in a mailbox accessed by Outlook 2003.”
Method 1: Install Update Rollup 1 for Exchange Server 2010
Important This method contains steps that tell you how to modify the registry. However, serious problems may occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For more protection, back up the registry before you modify it so that you can restore the registry if a problem occurs. For more information about how to back up and then restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
You can download Update Rollup 1 for Exchange Server 2010 from the following article in the Microsoft Knowledge Base:
976573 Description of Update Rollup 1 for Exchange Server 2010
After you install the update, you must add the following registry data to the server by using the Client Access role.
- Start Registry Editor.
- Locate and then click to select the following registry subkey: HKEY_LOCAL_MACHINESystemCurrentControlSetServicesMSExchangeRPCParametersSystem Create the ParametersSystem
Noteregistry subkey if it does not exist.
- Add the following registry data to the server:Value type: REG_DWORD
Value name: Maximum Polling Frequency
Value data: any integer between 5000 and 120000 (decimal value)
- Exit Registry Editor.
The registry change is dynamically detected. Therefore, the new settings will be applied to any new connections that clients make after the change is made. If you want to make sure that the new settings are applied to all clients, you should recycle the Microsoft Exchange RPC Client Access service because connections from clients can remain alive for a long time.
Outlook 2003 does not poll the Exchange Server 2010 server in intervals that are less than 10 seconds. Therefore, any value less than 10000 will generally have the same effect.
This change does not reinstate UDP communication between Exchange Server 2010 and Outlook 2003. This change only enables polling to occur more frequently between Exchange Server 2010 and Outlook 2003.
Microsoft KB – link
There is an issue with installing SP2 for Exchange 2007 on SBS 2008, Microsoft has released a tool to get passed the errors – link. You need to download and extract Exchange 2007 SP2 – link, run the install tool. It will ask for the directory of SP2, and then you install SP2 normally.
Here are more details of the issue on MSExchange.org
Here is a great article on how to install Windows 7 or Vista from a USB flash drive. It actually works as described.
When running WSUS on a Small Business Server, the default location is the C: drive, when that drive gets full you need to move the content and the SQL database. Below are the steps to move the SQL database to another location.
1. Open command prompt and type: net stop “update services”
2. Next, at the command promt type: net stop w3svc (if it is SBS 2008 it will also stop the Terminal Services Gateway, remember to restart)
3. Open Microsoft SQL Express Management Studio (if you don’t have this, go to http://tinyurl.com/ynl9tv to download) and connect to the MICROSOFT##SSEE database, which is the WSUS database and the SharePoint databases in SBS 2008. You can’t just connect to the database normally, you need to type this in server name area: \.pipeMSSQL$MICROSOFT##SSEEsqlquery
4. Detach the SUSDB database, move the SUSDB folder to the new location and attach the database again with Management Studio
5. Restart the services: “update services”, “w3svc”, and “Terminal Services Gateway”
While going through a vulnerability scan for PCI compliancy, the report noted that IIS 7 on a Small Business Server 2008 was still using SSL v2.0 instead of SSL 3.0 or TLS 1.0. To disable SSL v2.0:
- Click Start, click Run, type regedt32 or type regedit, and then click OK.
- In Registry Editor, locate the following registry key:HKey_Local_MachineSystemCurrentControlSetControlSecurityProvidersSCHANNELProtocolsSSL 2.0Server
- On the Edit menu, click Add Value.
- In the Data Type list, click DWORD.
- In the Value Name box, type Enabled, and then click OK.Note If this value is present, double-click the value to edit its current value.
- Type 00000000 in Binary Editor to set the value of the new key equal to “0”.
- Click OK. Restart the computer.
IIS negotiates the encryption with the client browser. An attacker could use a tool that tells the server it has only sslv2 (which is weaker) available. If you disable sslv2 it only uses v3 or tls, as requested by browser. A browser only supporting sslv2 would fail.
This applies to Windows Server 2003, and Windows Server 2008, and both versions of SBS.
I ran into an issue with a Hyper-V server with 6 NIC’s, some of the NIC’s in Network and Sharing center were being categorized as ‘unidentified network’ and giving the public designation. I could change it to private, but every reboot it would revert back. The issue with public network was that network discovery and file sharing was turned off, so even the NIC that was joined to the domain had little connectivity. Below fixed the issue.
You can change the security setting so that the network is not made public in the first place.
To do this on your local server or Vista/Windows 7 desktop , follow these steps:
1. Start –> run –> MMC –> press enter
2. In MMC console , from menu file select Add/Remove Snap-in
3. Select Group Policy Object editor –> Press Add –> select Local computer –> press OK –>press OK
4. Open Computer configration –>Windows Settings –>Security Settings –>select Network list manager policies
on the right Side you will see options for :
double click –>Unidentified networks
Then you can select the option to consider the Unidentified networks as private and if user can change the