(For 2008/Win7 you'll need to make sure that you have the Telnet client installed - an option from Add/Remove Programs or Server features)

c:\>telnet [routerip]

>sys reboot

Simples.

Simple. Or so you might think.

It would send me the file, but not update it first.

The gotcha, after a while of searching etc, was that you have to enter the script folder in the "Start in" field. Else it just won't work - and won't really give you any meaningful error messages.

Where [username] is the user who created the job.

Simple fix - start the service...

...Problem - you've got to do this manual process before you use the automated deployed. Doh. That's just silly!

Solution - use group policy to update computer configurations to set the Remote Registry service to start automatically.

So you want to update the Computer settings for the group policy that applies to all of your clients computers, particularly he ones that you are deploying the Sophos client to.

Open Group Policy MMC, navigate to Computer Configuration > Policies > Windows Settings > Security Settings > System Services

Find the Remote Registry entry, double click and set to 'Automatic'.

Allow the policy to refresh across the network (being a computer policy this *may* require a reboot - worth leaving it 24/48hrs to sink through). Now try and deploy the Sophos client again.

Doing something as simple as adding your domain to the default email policy - which will automatically create the smtp email address whenever a new mailbox is created - ends is an error.

(Organisation Configuration > Hub Transport > Email Address Policies > Default Policy)

Summary: 2 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:00

Edit Default Policy
Failed

Error:
The operation can't be performed on the default e-mail address policy.

Exchange Management Shell command attempted:
set-EmailAddressPolicy -ConditionalDepartment @() -ConditionalCompany @() -ConditionalStateOrProvince @() -ConditionalCustomAttribute1 @() -ConditionalCustomAttribute2 @() -ConditionalCustomAttribute3 @() -ConditionalCustomAttribute4 @() -ConditionalCustomAttribute5 @() -ConditionalCustomAttribute6 @() -ConditionalCustomAttribute7 @() -ConditionalCustomAttribute8 @() -ConditionalCustomAttribute9 @() -ConditionalCustomAttribute10 @() -ConditionalCustomAttribute11 @() -ConditionalCustomAttribute12 @() -ConditionalCustomAttribute13 @() -ConditionalCustomAttribute14 @() -ConditionalCustomAttribute15 @() -RecipientContainer $null -EnabledEmailAddressTemplates 'smtp:@domain.local','SMTP:@mydomain.co.uk' -Identity 'Default Policy'

Elapsed Time: 00:00:00

Apply Default Policy
Cancelled

Not that I know why it actually fails, but I do know how to get it to work. Instead of using the EMC GUI use the command line Exchange Management Shell and the following command with updating with your domain details.

Set-EmailAddressPolicy -Identity "Default Policy" -EnabledEmailAddressTemplates SMTP:@mydomain.com,smtp:@domain.local

Note that the upper-case "SMTP" dictates which address is used as the default reply to address.

Also it may not apply straight away - so to push it out to all mailboxes, you can go back to the EMC GUI > Organisation Configuration > Hub Transport > Email Address Policies > Default Policy, Right click on the Policy and choose Apply...

http://www.safeguardict.com/blog/?p=66

Here's a quick fix of how to avoid it:

http://social.technet.microsoft.com/Forums/en/winserverTS/thread/87fc497a-27fd-4a76-ab59-ea5fe01c9091

Naturally we now deploy this to all of our clients with Remote Desktop servers.

All you need to do is enable the rule:

1. Start Menu
2. Control Panel > Administration Tools
3. Windows Firewall with Advanced Security
4. Inbound Rules
5. File and Printer Sharing (Echo Request - ICMPv4-In) (v6 too if you are in the future!)
6. Right-click and choose Enable Rule
7. Et voila!

I had created a new Windows 2008 R2 (x64) Remote Desktop Host (a.k.a. Terminal Server) for one of our clients who still using Office 2003. Naturally they are receiving documents on 2007/2010 format with the xlsx format.

It all sounds simple. Just install the OS, the Apps and the compatibility pack. Not so - you won't be able to open .xlsx files or save files to .xlsx format.

The secret is that you need to set both the Excel Shortcut and C:\Program Files (x86)\Microsoft Office\Office12\excelcnv.exe to run in compatibility mode to run for XP SP3.

Since it's a Terminal Server remember to "Change the settings for all users"