Monthly Archives: September 2013

You are browsing the site archives by month.

It really is not supported next year

Let’s try this again with an updated chart on the SBS blog:


http://blogs.technet.com/b/sbs/archive/2013/09/25/information-about-sbs-2003-product-support-lifecycle.aspx


The Extended Support End Date for the following products is as follows:


Products Released

Extended Support End Date

Exchange Server 2003 Standard Edition

4/8/2014

Windows SharePoint Services 2.0

1/14/2014

Internet Security and Acceleration Server 2004 Standard Edition

10/14/2014

SQL Server 2005 Workgroup Edition

4/12/2016

Windows Server 2003/2003 R2, Standard Edition (32-bit x86)

7/14/2015

Windows Server Update Services 3.0

7/11/2017


Windows server 2003 will no longer be supported in 2015.


The lack of support is more than just security updates….. if you get stuck in migrating from Exchange 2003, in a server down situation where you are trying to recover email… you will get no support from CSS.  You will be on your own for migration. 


I can’t stress this enough… you really need to decide the future on these boxes you still have out here.

PSconfig – I’m lazy

So to do some testing on a SBS 2011 I was building a brand new one.. and 47 gazillion updates later and about 40 psconfigs (okay more like three so far) at about the second time doing a psconfig command I realized there has to be a better way.


So whether you are a command line person, a bat file person a powershell person….what I did for me since I’m a .bat command line gal, is I stuck a little .bat file in the Windows\system32 folder


The name of the file is psconfigbat.bat


The contents of psconfigbat.bat is as follows:


CD\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures


That’s it.  Save it as a .bat file and dump it into the c:\windows\system32 folder just because that’s where you end up when you runas admin at the command com icon.


When I run a Sharepoint update, I then go to the command com icon on the start menu, right mouse click run as admin and then type in psconfigbat and hit enter


The command then does it’s thing.


 

So why is Microsoft charging more?

A bit of background – I spotted these Ehrman needlepoint kits and wanted the Paris and Eiffel Tower kits.  But I soon found out that they no longer had the Eiffel Tower one in stock.  So we searched around and found an Australian firm that still had one in stock.  I was a bit surprised to see that the AU to US conversion on the site was nearly dollar for dollar.

So first thank you for having a Sydney needlepoint store that carried the Eiffel Tower needlepoint kit – and apparently I got the last one in stock.

http://morrisandsons.com.au/c2_123_658/44694/

http://www.ehrmantapestry.com/Products/Paris__PARIS.aspx
http://www.ehrmantapestry.com/Products/St-Tropez__STTROP.aspx


But that got me to thinking… the US to AU is near dollar for dollar now….

http://www.rttnews.com/2194575/australian-dollar-drops-to-10-day-low-against-us-dollar.aspx


so why is Microsoft able to charge more in AU than here?  Yeah I know just because they can….but just because they can isn’t good business in the long run.  People will look for options, yes?

Ready for a licensing blog post?

Did everyone catch this really good blog post on Essentials licensing?


Essentials 2012 R2 – The Role & Licensing | Title (Required):
http://titlerequired.com/2013/09/17/essentials-2012-r2-the-role-licensing/

It’s dead in April folks.

Information about SBS 2003 Product Support Lifecycle – The Windows Server Essentials and Small Business Server Blog – Site Home – TechNet Blogs:
http://blogs.technet.com/b/sbs/archive/2013/09/25/information-about-sbs-2003-product-support-lifecycle.aspx


Dudes, just say that April 8, 2014 it’s in effect dead because Exchange … you know the main reason we’re still running it… is when it goes out of support.

Now THAT’S customer service!

I had purchased a 20 piece Libbey Ramekin set – 10 glass ramekins and 10 plastic lids as I got into a kick of making PannaCotta after a trip to Italy this summer.  The Ramekins are the perfect size and the plastic lids make placing them in the refrigerator nice and easy to keep both the fridge clean as well as let the desserts set up nicely.  And one evening while cleaning up I realized that we’d lost a plastic lid.  We figured it accidentally got dumped into the garbage and attempted to dig into the can to find the missing lid but when we realized that the garbage had already been emptied into the large curbside can, we started to search for it and then decided not only was it going to be difficult to find the clear plastic lid, we might end up buried in icky garbage in the process. 


So I thought, okay,  I’d just find a replacement one instead.  Well, the ones I bought from Amazon that were really made for pet food lids weren’t quite the right size.  So my sister encouraged me to reach out to Libbey and see if their customer service could help me.  I didn’t see any place on their web site to order replacement lids but they clearly had an 888 number to call and contact them for customer service.


And what fantastic customer service it was indeed!  Imagine my surprise to have the phone call answered by a nice friendly female voice.  I explained my problem, of losing a lid for the ramekin sit and she said “Hang on, I think I have the exact size you need here”.  You could hear her checking the size and she proclaimed that indeed she had the replacement lid.  She instructed me to send an email to a libbey customer service email address and place my address in the email along with indicating the lid I needed. 


Today to my delight, in a Libbey legal envelope with my address hand written on the front, came not one, but two replacement lids.



Thank you LIbbey for reminding me what really great customer service is all about!


For anyone interested:


(1) PannaCotta recipe


3 cups cream
1 cup whole milk
3 and 1/2 sheets of Gelatin sheets (gold or platinum strength)
Let the sheets soak in the cream for a little bit before cooking
Place pan on stove and bring to 135 degrees (use a cooking thermometer)

When 135 degrees, remove from heat and stir in 6 tablespoons of Sugar.
Now add various flavorings such as:
1 teaspoon of vanilla
1 teaspoon of orange extract
1 tablespoon of Grand Marnier


Stir until the sugar is dissolved.


Now pour the liquid into 6 to 7 glass Ramekins from LIbbey and place in your fridge overnight.

Eat as is or with fresh fruit.  I like it with fresh strawberries, fresh peaches and fresh nectarines with an extra dollop of whipped cream on top.

Last known good bug

Background:  This is an issue seen in Windows 2008 r2 and Windows 7.  It is probably also seen in Windows 2012, 2012 R2, Windows 8 and now Windows 8.1.  While we’ve seen it most often in Small Business Server, (Amy Babinchak just hit it the other day and inspired this blog post) it can also happen in workstations.  A past forum post showcases this issue is not new:  http://social.technet.microsoft.com/Forums/windowsserver/en-US/8210cfc3-f424-4550-86a9-b0a70a1569b3/last-known-good-changed-the-computer-name  
Normally last known good will work as it should and allow you to boot into the last time you had a successful boot as noted in http://blogs.technet.com/b/askcore/archive/2011/08/05/last-known-good.aspx  But in a fact pattern I’ll call the “Last Known Good” bug, there’s a sequence of issues that will cause a major issue with the booting of the domain controller.  This will impact anyone outside of the Pacific time zone – that is anywhere from UTC-7 to UTC+11:30
Symptoms:  The computer name is correct when viewed in properties of Computer. However the DNS server shows a computer name Win-XXXXXXX, Active Directory is unable to start and NetLogon Service doesn’t not start.  Your event log is filled with errors such as:
Log Name:      System
Source:        NETLOGON
Date:          9/20/2013 11:13:43 PM
Event ID:      5602
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server.domain.local
Description:
An internal error occurred while accessing the computer’s local or network security database.

Log Name:      System
Source:        Microsoft-Windows-GroupPolicy
Date:          9/20/2013 10:54:22 PM
Event ID:      1110
Task Category: None
Level:         Error
Keywords:     
User:          DOMAIN\Administrator
Computer:      Server.domain.local
Description:

The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account.

Log Name:      System
Source:        Microsoft-Windows-DfsSvc
Date:          9/20/2013 10:50:16 PM
Event ID:      14548
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server.domain.local
Description:
The DFS Namespace service could not initialize the trusted domain information on this domain controller, but it will periodically retry the operation. The return code is in the record data.



Symptoms you will see is that nothing works as expected.  When you log in if you try to switch to the local machine, you will see the wrong computer name.  If you are in this situation you will need to fix the registry keys, and will have to dig through the current set that are wrong.  If you are fixing the registry offline, you will need to find the proper hive that is the current one and fix that.

Remedy:
Before starting a server installation, go into the machine BIOS (if on physical hardware) and set the time as if it were in PST (UTC-8), so If it is say 5 p.m in the central time zone where you are, set the computer to be 3 p.m pacific time on the server before you start installing the machine from the first DVD.
If you are using a virtualized server, leave the sync time option running in the hypervisor in Server 2008r2 and higher.  If this is not possible, set the host to PST during the setup.



To detect and prevent the issue:
24 hours after the initial deployment of a SBS installation, if you ever plan to use the last known good boot option check and compare the control set values:
Click on start, run type in regedit and run as admin
•    Compare the values in Current and last known good for the following entries:
•    HKEY_LOCAL_MACHINE\SYSTEM\Select
•     
•    As you can see Current is a value of 1, LastKnownGood as a value of 2
•    Now expand the trees for Current and LastKnownGood and compare the values in:
•    HKEY_LOCAL_MACHINE\SYSTEM\ControlSetnnn\Control\ComputerName\ComputerName
•     
•     If they don’t match, then you are exposed to this and if you happened to use the Last Known Good Configuration you will boot your server and find out its name has reverted to its original deployment name.
To correct this issue:
1.    You will need to refresh the current control set, by opening the following path:  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ComputerName.  Select it, and then select File->Export, save it locally just in case.
2.    In that same ComputerName key, create a NEW string value (right click, now click on new string value). Take the default name and leave the value blank.
3.    Delete the newly created string value. So at the end of step 2 and 3 you are left with everything looking just like it did back in step 1.
4.    Close regedit and reboot.
5.    After reboot, check the last known good set values as per the first set of steps.

Just a fyi – both Exchange and SharePoint are not supported on R2 at this time.

http://blogs.technet.com/b/wbaer/archive/2013/09/22/sharepoint-2013-support-for-windows-server-2012-r2.aspx


Currently, Microsoft SharePoint Server 2013 is not supported for installation on computers running the Windows Server 2012 R2 operating system.   Installing SharePoint Server 2013 on a computer that is running Windows Server 2012 R2 could lead to unexpected behavior, therefore, Microsoft does not support SharePoint Server 2013 in Windows Server 2012 R2.


SharePoint Server 2013 with Service Pack 1 and SharePoint Foundation 2013 with Service Pack 1 will offer support for Windows Server 2012 R2. The release date for Service Pack 1 for SharePoint Server 2013 and SharePoint Foundation 2013 is to be determined. This article will be updated as more information becomes available.


 


Just a fyi – both Exchange and SharePoint are not supported on R2 at this time.

Heads up for a bug in 2012 R2 HyperV

Just a heads up for those that are starting to play with 2012 R2.  


http://www.reddit.com/r/sysadmin/comments/1mmxhg/psabug_hyperv_built_on_r2_code_base/


A bug has been found in the RTM code of 2012 R2.


If you set up the guest/child virtual machines “If you select “Shut Down the guest operating system” as the automatic stop action, the Shut Down command will not be sent, it issues the Turn Off command and doesn’t gracefully shutdown the machines.”


For the time being until this RTM bug is fixed, I would advise you to select save or manually shut down the operating systems before you reboot the parent.  


Microsoft may be kicking VMware’s butt in virtualization…but I think Microsoft doesn’t have all the bugs worked out in the code.  So you might want to keep that in mind when evaluating 2012 R2.

Two adjustments I make on iOS 7

I go into general


Then to accessability


Then I change


BOLD TEXT to on (the phone will need a reboot)


and then also change Increase Contrast to On


Otherwise it’s a bit white and uh… well… Win8 metroish for my old ancient eyeballs.