• Enable TRIM (Should be enabled by default)
• Disable Prefetch
• Disable Superfetch
• Disable Indexing
• Disable Write Caching
• Disable System restore
• Disable Hibernate
• Disable Page file (only if you have a lot of RAM)
• Disable De-fragmentation

Therefore, it is best to turn off this redirection as a precaution. This process can be performed on Windows Server 2008 R2 and Windows Server 2012.

1. Open an Administrative Command Prompt, and Start the Microsoft Management Console (MMC).

   

    

2. In the Console, navigate to Add/Remove Snap-in

   

    

3. Select and add the Group Policy Object snap-in.

   

    

4. Click Finish to apply the Snap-in to the Local Computer.

   

    

5. Click OK, to close the Snap-In window.

   

    

6. Expand the Snap-in to Console Root/Local Computer Policy/Computer Configuration/Administrative Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/Printer Redirection

   

    

7. Double Click on “Do not allow client printer redirection” and Enable the setting. Click Apply, then OK.

   

    

8. Log off the session to apply the setting.

The solution is to disable (NOT DELETE) the CGI-exe and ISAPI-dll modules on the SBS Client Deployment Applications Website in IIS.

1. To do this, you need to start up the Internet Information Services (IIS) Manager. Note: There are 2 of these located in Administrative tools. Select the non-numbered (version 7) one.

   

2. Expand to the SBS Client Deployment Applications Home and locate Handler Mappings.

   

3. Double-Click Handler Mappings. Then locate CGI-exe. Right-Click and Edit Feature Permissisons.

   

    

4. Remove the tick on Execute. You will not see CGI-exe and ISAPI-dll listed in the disabled section. Click OK.

   

    

5. Return to the SBS Client Deployment Applications Home, right-click on the website, select Manage Web Site, and restart the site.

   

Fortunately, you can enable a SMTP service that is built into the core operating system for Windows Server 2012. Here how to do this.

Install the SMTP Service

1. Launch the Server Manager. From the Search charm, type in Server Manager to find it.

   

    

2. From the Dashboard, Add Roles and Features. The Add Roles and Features Wizard will begin. Click Next on the first screen.

   

    

3. Select Role-based or feature-based installation.

   

    

4. Select the Essentials Server (which should be highlighted by default).

   

    

5. Click Next to bypass the Roles selections.

   

    

6. Scroll down the list and tick the SMTP Server feature.

   

    

7. A new window will pop up to inform you that some other services will also be installed. Click Add Features to confirm and continue. Click Next to continue past the features selection screen.

   

    

8. Click Install to complete the Installation.

   

    

9. Click Close when the installation has completed.

   

    

Configure the SMTP Service

1. From the Search charm, type IIS. Hover your mouse over one of the selections, and run the Internet Information Services (IIS) 6.0 Manager.

   

    

2. Click Yes to the UAC Prompt.

   

    

3. Expand to SMTP Virtual Server #1, right click and select Properties.

   

    

4. General Tab: Set the IP Address to the server’s IP address.

   

    

   Note: You can also enable logging is required.

    

5. Access Tab: Set the IP for the internal devices in the connection button.

   

    

   Add the same IP to the Relay list.

   

    

6. Delivery Tab: Set an external domain – you can use the free customised domain from Microsoft, and you can also optionally add a Smart host, if required. Tick the Attempt direct delivery box, if you want the server to attempt to deliver the email directly first before trying the Smart host.

   

    

7. From the Search charm, type Firewall to locate and run the Windows Firewall with Advanced Security console.

   

    

8. Add a new Inbound Rule. (Right Click on Inbound Rule, and select New Rule)

   

    

9. Select Port.

   

    

10. Type in 25 as the local port.

    

     

11. Click Next (Allow the Connection).

    

     

12. Uncheck Public. (Prevents external access to the server)

    

     

13. Give the rule a name, and click Finish to create the rule.

    

     

14. You should now see a new rule enabled in the firewall management console.

    

     

15. Restart the SMTP Service and set the service for Automatic Start. Open up the Services Management Console. Double Click on the Simple Mail Transfer Protocol service. Stop and then Start the service. Set the Startup type to Automatic.

    

     

That’s it. The service is ready and waiting.

NOTE: You can also do this with Small Business Server 2011 Essentials, and also with Windows Server 2012 or Windows Server 2008 R2. With SBS2011 Essentials and Server 2008 R2, there is a slight difference in adding the SMTP Service role, but it is a fairly straightforward task.

Once the hotfix has been applied, you can then enable the WSUS role on a server running WS2012 Essentials. You can read more about how and what WSUS is from the Microsoft Technet article here – http://technet.microsoft.com/en-us/library/hh852345.aspx

A word of thanks to the HP Coffee Coaching Team, MVPs and IT Pro Community who have campaigned to have this feature enabled in WS2012 Essentials.

Granted, this is not new for those who have purchased a Volume License agreement. However, not many realise that this is also available in the System Builder or OEM channel.

There is a lot of information on the OEM Partner Center here – http://www.microsoft.com/oem

Therefore, if you are running WS2012 as a HyperV Host, you can install up to two virtual servers, which can be any of the following – WS2012 (standard or datacentre), WS2012 Essentials, WS2011 Essentials, WS2008R2, WS2008, WS2003.

The big question is “How to I activate the servers?”

To downgrade the virtual servers, you will need to implement the following steps:

1. Obtain genuine Windows Media and a corresponding product key.
   1. It should come from a previously legally licensed version from the OEM or Retail channel. (Yes, that is correct! You can grab a DVD and a product key from a previously activated and installed server. It does not have to be yours)
   2. If you have a volume license agreement, then you must use the volume license media and product keys.
2. Install the virtual server using the media and corresponding product key above.
3. When the server needs to be activated, you can attempt to do this online. If it works, great! If you are not able to activate the product key because it had been previously activated, you will need to call the Microsoft Activations service.
   1. Call the number as listed for your country. http://support.microsoft.com/kb/950929
   2. Select Windows or Windows Server activation.
   3. Type in the installation ID as shown on your screen and wait to be transferred to a service representation.
   4. Explain to the representative that you are downgrading your WS2012 installation and need to activate the WSnnnn installation.
   5. When asked, provide the installation ID, and the representative will provide you with the confirmation ID to activate the server.

Note that the other OEM licensing rules still apply. You cannot transfer this license to another physical machine, nor can you put the virtual machines on another physical host. The host and the virtual machines must live and die on the physical machine that they are licensed for.

“Congratulations! We are pleased to present you with the 2013 Microsoft® MVP Award! This award is given to exceptional technical community leaders who actively share their high quality, real world expertise with others. We appreciate your outstanding contributions in Small Business Server technical communities during the past year.”

As the independent voice of users worldwide, your influence on technical communities is felt in many ways—enhancing people’s lives and contributing to our industry’s success. We’re deeply grateful to you for sharing your feedback, comments, answers, and expertise with technical communities. In recognition of your commitment, Microsoft is pleased to honor you with the Most Valuable Professional Award. Thank you for empowering the community with your outstanding leadership! Steven A. Ballmer Chief Executive Officer Microsoft Corporation

Thank you for your exceptional contributions to technical communities! It gives us great pleasure to present you with the Microsoft Most Valuable Professional Award for the technical expertise you generously provide to others. By sharing your knowledge, experience, and objective feedback, you inspire and help people to solve problems and discover new capabilities every day. We are honored to welcome you as a Microsoft MVP. Rich Kaplan Corporate Vice President Customer and Partner Advocacy Microsoft Corporation

Email traffic may be affected over the next few days.

The original post covering previous versions of outlook can be found here – http://blog.powerbiz.net.au/registry-hacks/where-is-the-temporary-outlook-folder/

For Outlook 2010, the registry location which shows the location of the Outlook Temporary Folder is HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Security.

For Outlook 2013, the registry location which shows the location of the Outlook Temporary Folder is HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Security.

At the log in screen, you may see this message.

Upon logging in, you may be faced with the prospect of the server rebooting in 15 minutes. The countdown timer has started and there is no apparent way to click on a “Postpone” button.

In many cases, this will cause some distress. Particularly if this is a Hyper-V host server, and you have an entire network of 120 users accessing the virtual machines!

Fortunately, there is a fix to prevent the server from counting down and restarting.

1. Open an administrative command prompt.
2. Type NET STOP WUAUSERV
   to stop the Windows Update service.

This will stop the Windows Update service, and stop the countdown timer until the server is restarted manually. Don’t forget to restart the server at the next possible opportunity.