Windows Server 2012 Essentials: Shutdown client machines after a backup

WSSE_LogoA client of ours who is running a Windows Storage Server 2008 R2 Essentials on their SBS 2011 Standard network (for client PC Backup) Logolikes their machines to shutdown each night after a backup.

This could apply to any of the Essentials Server SKUs including SBS 2011 E, WHS 2011 or Essentials 2012. 

We schedule the backups to run between 7pm and 11pm so all the machines will have time to backup. It is really simple to set this shutdown task up, of course some people prefer their machines to go to sleep or hibernate but in this case we actually want to turn off those machines.

Read more of this post

Quick Fix : Update SBS2011 Essentials Windows 7 Pro Pack for Windows 8

sbse-conNice title for a post, hopefully the SEO on that one will kick in.

Had a question come into one of my mailboxes about the Windows 7 Pro Pack and making the GPOs apply to Windows 8.

If you recall, SBS 2011 Essentials launched an Addin to push out some preconfigured GPOs to clients for security settings and folder redirection. I covered the WMI filters in a post about how to extend that functionality to Windows XP and Windows Vista.

Running a GPResult /R on a Win8 client, we can see that our custom GPOs that use WMI filters, are not being applied.

Read more of this post

Windows Server 2012 Essentials HP Printer Unspecified Device

LogoI recently did a post about adding a Printer to an Essentials server, i thought i had covered all the bases, however i have seen several questions pop up on the forum regarding HP Printers appearing as unspecified devices when connected via USB. This presented me with a unique challenge as all my lab kit is on HyperV. However i do have a USB HP printer in the office, so i hooked it up with a long USB lead to a MicroServer, and set about trying to repro the problem.

Read more of this post

PowerShell, Make it do something useful!

powershell2xa4$users = ((Get-ADUser -filter * | where-object { $_.GivenName -ne $null }) | foreach{ $_.Name})
foreach ($user in $users)
{
        $FirstName = (Get-ADUser -filter {Name -eq $User} | foreach {$_.GivenName}).ToString()
        $SurName = (Get-ADUser -filter {Name -eq $User} | foreach {$_.SurName}).ToString()
        $DisplayName = ("$Firstname" + " " + "$Surname")
        $DisplayName
        Set-ADUser $User -DisplayName $DisplayName
        Set-ADUser $User -Description "User Created by Windows Server 2012 Essentials Dashboard"
}

You might be wondering what the hell that means?

Read more of this post

Windows Server 2012 Essentials : Add a Network Printer

LogoI have seen and heard of people struggling to install printer drivers in mixed x64 and x86 environments, it has been a problem for a long time now, probably as far back as XP x64, certainly it was an issue with SBS 2008.

The problem being in order to install a printer on the Server, you need the x64 bit driver, but on a client pc you may be on x86 (32Bit) Windows, so you need a different driver.

Essentials 2012 is no different. So, i thought i would just get an example together using a printer i have here in the office, an HP Laserjet 3055. This is a good example actually because when you install it to WSE12, it picks up a valid driver, but there is no equivalent driver for Windows client available from HP.

Read more of this post

On Prem Exchange Windows Server 2012 Essentials: The Script!

Exchange2A few months back, i posted up about how to deploy the On Premises Integration between WSE12 and Exchange.

powershell2xa4As part of that post i completely glossed over the method to install the Exchange Server promising to publish the PowerShell script i had written ‘soon’.

Today, my great friends, is that day.

Read more of this post

Enable DirectAccess on Windows Server 2012 Essentials

Logo

This post is now quite out of date and the instructions within are no longer reliable. Please refer to Microsoft’s own document online for the relevant steps.

http://technet.microsoft.com/en-us/library/jj204618.aspx

One of the coolest improvements in Server 2012, is the simplification of DirectAccess. Not just the steps to enable it, but the requirements for your infrastructure to support it. In the past it was beyond most SMBs due to the need to have 2 consecutive public IPs a dedicated DA server, IP 6to4 translation capable equipment, and not to mention Windows 7 Enterprise, which few SMBs deploy. Moving into the 2012 line of products DA has become much more available to SMBs with the reduction in infrastructure requirements. Taking Essentials as an example, we can now run DA using just a standard Internet connected router, and with just our Essentials box as the DA endpoint.

Read more of this post