Monthly Archives: May 2013

You are browsing the site archives by month.

WSUS role on Essentials?

Want to know how to install the WSUS role on Essentials?


Robert Pearman has the details:


http://titlerequired.com/2013/05/31/enabling-wsus-on-windows-server-2012-essentials/

Require Windows 2012 Server to install updates and reboot at certain time

FAQ] Require Windows 2012 Server to install updates and – Microsoft Partners Forum:
http://partnersupport.microsoft.com/en-us/mpndataplat/forum/mpncatwinsvr-mpnws2012/faq-require-windows-2012-server-to-install-updates/1c383728-6d77-4efa-9034-e0e1880dd899
Forum Moderator
[FAQ] Require Windows 2012 Server to install updates and reboot at certain time

Issue:

Require Windows 2012 Server to install updates and reboot at certain time


Solution

You can set the following registry key to force the Windows server 2012 to reboot.


Registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU

Value: AlwaysAutoRebootAtScheduledTime

Type: REG_DWORD


Value data: 1 (force a restart)

 
For more information, please go to the following KB:

How to force automatic restarts after important updates in Windows 8 and Windows Server 2012

http://support.microsoft.com/kb/2835627

One month and seven months to go


That’s an example of “grow my own”.  I grew the tomatoes and basil on that plate.  We are at one month and seven months away from “Grow your own” small business solution.


It’s a reminder that we are at one more month of volume license selling of Small Business Server 2011 standard and Premium add on – so if your client is on SBS 2003 and was on the fence about on premises email, now is the time to sit him or her down and tell them they will be planting their own SMB crops in a few short months.


VL sales for SBS end 6/30/2013, OEM ends 12/31/2013.


Now’s the time to sit them down and determine what you’ll be planting in the future.

So what’s supported?

Working on the next doc for the SMB Kitchen project – this one detailing out what is supported where….


Did you know that Exchange isn’t exactly blocked from being installed on a Domain controller?


In large enterprises, domain controllers are single purpose servers that only serve one role.  In Small business we do not always have the resources to plan our deployment such that the domain controller can be on its own server.  There are certain server roles that are blocked from deployment or blocked from support when combined with a domain controller. 


Exchange Server:  While not recommended to be installed on a domain controller, it’s not officially blocked to install Exchange on a domain controller as long as the server is Windows 2012 standard.  On Windows 2012 Server Essentials, Exchange is not supported to be installed on top of the Essentials server.  As noted in Technet (Microsoft) when you go to install Exchange 2013 on a domain controller, you will get a warning:


“Microsoft Exchange Server 2013 Setup has detected that the computer you’re attempting to install Exchange 2013 on is an Active Directory domain controller. Installing Exchange 2013 on a domain controller isn’t recommended.”


The Technet documentation goes on to state the following statements in bold.  The SMB implications of these statements is italicized.


If you install Exchange 2013 on a domain controller, be aware of the following issues:


Configuring Exchange 2013 for Active Directory split permissions isn’t supported.  This typically is not an issue in a small firm where the physical implementation of the network limits the permissions to just that physical implementation.


The Exchange Trusted Subsystem universal security group (USG) is added to the Domain Admins group when Exchange is installed on a domain controller. When this occurs, all Exchange servers in the domain are granted domain administrator rights in that domain.  In a small firm, typically there is only one Exchange server.


Exchange Server and Active Directory are both resource-intensive applications. There are performance implications to be considered when both are running on the same computer.  If you place Exchange on a domain controller, you need to properly size the physical server.  It will need ample amounts of RAM, ample disk speeds and I/O.  Any memory recommendations by Microsoft need to be increased for real world deployment.


You must make sure that the domain controller Exchange 2013 is installed on is a global catalog server.  In the case of a small firm, this is typically a non issue.


Exchange services may not start correctly when the domain controller is also a global catalog server.  This is a serious issue and one that has often plagued Small Business Server.  For Small Business Server it was recommended to follow method 2 or 3 of http://support.microsoft.com/default.aspx?scid=kb;en-us;940845 (see http://blogs.technet.com/b/sbs/archive/2011/03/24/exchange-services-may-not-start-automatically-after-a-reboot.aspx for background)


• System shutdown will take considerably longer if Exchange services aren’t stopped before shutting down or restarting the server.  SBS suffered from this and many folks scripted a shutdown of Exchange services in order to reboot faster (see http://msmvps.com/blogs/bradley/archive/2007/11/17/charlie-russel-on-shutdown.aspx )


Demoting a domain controller to a member server isn’t supported.  Typically in SMB demoting a domain controller isn’t often done.  However, once you install Exchange on a domain controller you can never undo this process.


Running Exchange 2013 on a clustered node that is also an Active Directory domain controller isn’t supported.  If you plan any hyperV clusters, you cannot place it on a domain controller.


We recommend that you install Exchange 2013 on a member server.


Ultimately the issue is one of support.  If you place Exchange on your domain controller, support can ultimately push back on supporting you in this configuration.  Therefore for the SMB server of the future, it’s recommended that Exchange be on a member server.

Got Australian Quickbooks?

Showcasing that not all versions are alike


QuickBooks Australia Premier 2012/2013:
http://www.quicken-asia.com/products/quickbooks-australia-upgrade-version/quickbooks-australia-premier


  • Microsoft .NET Framework Common Language Runtime 1.1 (provided on QuickBooks Installation CD. Requires an additional 150MB)

  • Microsoft .NET Framework Common Language Runtime 2.0 (provided on QuickBooks Installation CD. Requires an additional 150MB.)

  • .NET 1.1 is the kiss of death on SBS 2011


    http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/25f64560-029d-464e-b5f4-ca13a485a094/


    If you live in Australia keep that QuickBooks install away from that server.


     

    Messy, huh?


    Well I’ve been making a mess today, how about you?


    Happy pre-Memorial day to everyone in the USA.  Here’s hoping that one day we decide that wars and fighting don’t solve much.

    Office – garage series

    Office Blogs – Garage Series: The new Office, thriving in a virtualized world:
    http://blogs.office.com/b/office_blog/archive/2013/05/22/garage-series-the-new-office-thriving-in-a-virtualized-world.aspx


    If you haven’t been following the Office garage series I highly recommend it.  Like I didn’t know that clicktorun got patches differently than it’s ISO counterpart.


    And we may HATE how Office is licensed for RDP purposes… but check out the Garage series regardless


     

    Looking for how to build a hosted email add in for Essentials?

    http://msdn.microsoft.com/en-us/library/jj991858.aspx


    If you are looking for an example of how to build a hosted mail plug in for Essentials you can now download the sample from Microsoft


    Download it from here http://www.microsoft.com/en-us/download/details.aspx?id=34860


    And the sample files are then installed on your machine


    What a Windows RT device does

    Makes a great rdgateway device


    Makes a great RWA device (normal non metro IE supports ActiveX)


    I must say that the Dell AT&T AllAccess app which touts that you can set it up via the device leaves a LOT to be desired.  I had to call AT&T to set up the cellular I could not do it straight from the device even though the paperwork said I should.


    The other fail is that you can’t set up firm email without FIRST setting up a Microsoft account.   Only then do you get the option to add another account, and I can’t figure out how to not have an Outlook (cloud) account.  Hello Microsoft I realize that you think RT is a consumer device but I know a lot of consumers that don’t want an Outlook account.


    Last fail is that you have to update the apps installed on the store for each user’s profile you set up.


    Bottom line works well for what it does, but Enterprises are going to hate some of the design decisions on this.


    Control of patching, control of deployment, just not here….

    Nothin’ like system tray advertising


    If you have an older Adobe reader you’ll notice that your system tray now urges you to update.