Monthly Archives: September 2011

You are browsing the site archives by month.

The perils of being a female geek

So I arrive at the Rio hotel and start to unpack … the technology.   The wireless router so that I can make the wired connection a wireless (and btw if you are on a certain floor near a certain room the open wireless with the SSID of “default” is my little travel dlink router), and then the ancient laptop that I’ve had forrreeeever (and I’ll probably install win8 on it just as a proof of concept one of these days), and then the newest geek gear, an android tablet with a mifi device.  And I go to check to see if the mifi is charged up and…. shoot I remember I left the charger in the wall at home.  No worries, I’ll just use the USB connection jack to charge it like I do with my iPhone.  I use a retractable iPhone cable on the road so I don’t have to pack one more cable and I leave it in my laptop bag.  So I go to get the mini usb cable for it… and of course I can find like THREE mini usb cables in all of my geek gear but not the RIGHT mini usb cable.  Shoot, says I.  Well I’ll just have to use the mifi lightly this weekend. 


So I start to unpack a bit more and get things like my toothbrush out of my makeup bag.  And out of my makeup bag falls the RIGHT mini usb cable for the Verizon mifi device.


Why the RIGHT cable ended up in my makeup bag, I have no clue.  I’m going to guess in the heat of packing during the last trip I stuffed in in there, needless to say I’m now back to being a happy female geek with all my cables and cords and stuff and makeup and curling iron, and hot chocolate (yes I travel with bags of Hot chocolate – and good thing too – the Rio makes you pay for the coffee).


Well enough blogging for the night. time to get ready for Harry Brelsford keynote bright and early tomorrow morning.

SBS 2011 bpa updated!

http://support.microsoft.com/kb/2600333
http://blogs.technet.com/b/sbs/archive/2011/09/29/windows-server-solutions-bpa-updated-september-2011.aspx

Okay gang kick the tires, see if it now finds stuff.

New best practices

After you install this update, the Windows Server Solutions BPA performs the following checks:
  1. Checks whether the application pool for Remote Web Access uses the default account
  2. Checks whether the application pool for Remote Web Access uses the default version of the .NET Framework
  3. Checks whether the application pool for Remote Web Access uses the default Managed Pipeline Mode
  4. Checks whether the application pool for Remote Web Access uses the default bit version
  5. Checks whether the built-in Administrators group has the "Log on as a batch job" user right
  6. Checks whether the Windows Firewall is enabled
  7. Checks whether the DNS host (A) resource record points to the correct IP address
  8. Checks whether the internal network adapter is configured to register the IP address of the network adapter in DNS
  9. Checks whether the values of the DNS ForwardingTimeout registry key and the RecursionTimeout registry key are identical
  10. Checks whether the extension mechanisms for DNS (EDNS) is enabled
  11. Checks whether the forward DNS zone of your Active Directory domain allows for secure updates
  12. Checks whether the forward DNS zone allows for secure updates
  13. Checks whether Internet Explorer Enhanced Security Configuration is enabled for the Administrators group
  14. Checks whether Internet Explorer Enhanced Security Configuration is enabled for the Users group
  15. Checks whether the source server is in the Active Directory Sites and Services snap-in
  16. Checks whether the source server is in the SBSComputer organizational unit (OU)
  17. Checks whether the MaxCacheTTL DNS parameter is not set
  18. Checks whether a Windows Small Business Server (SBS) Group Policy is missing 
  19. Checks whether there are DNS name server resource records in the forward lookup zone
  20. Checks whether there are DNS name server records in the _msdcs zone
  21. Checks whether there are DNS name server records for the delegated _msdcs forward lookup zone.
  22. Checks whether Windows SBS is the Domain Naming Master (if Windows SBS is the Domain Naming Master, you will receive a confirmation message)
  23. Checks whether Windows SBS is the Infrastructure Master (if Windows SBS is the Infrastructure Master, you will receive a confirmation message)
  24. Checks whether Windows SBS is the Primary Domain Controller Master (if Windows SBS is the Primary Domain Controller Master, you will receive a confirmation message)
  25. Checks whether the Authenticated Users group is a member of the Pre-Windows 2000 Compatible Access group
  26. Checks whether Windows SBS is the Relative ID (RID) Master (if Windows SBS is the RID Master, you will receive a confirmation message)
  27. Checks whether the DNS client is configured correctly
  28. Checks whether Windows SBS is the Schema Master (if Windows SBS is the Schema Master, you will receive a confirmation message)
  29. Checks whether the value of the RootVeer registry entry for the .NET Framework is correct 
  30. Checks whether the server cannot ping
  31. Checks whether the value of the Remote Desktop Protocol (RDP) port is the default value
  32. Checks whether the value of the SysvolReady registry key is correct
  33. Checks whether the Sysvol folder is shared
  34. Checks whether the free disk space is very low
  35. Checks whether the value of the default Application Pool is changed
  36. Checks whether the Certification Authority name may cause errors
  37. Checks whether the value of the OriginalMachineName(90) registry key is correct
  38. Checks whether the value of the OriginalMachineName(100) registry key is correct
  39. Checks whether the version of Exchange Server 2010 is the release version
  40. Checks whether Windows SBS is in a journal wrap condition
  41. Checks whether the external remote procedure call (RPC) authentication is not set to the default method
  42. Checks whether the internal RPC authentication is not set to the default method
  43. Checks whether the version of Windows Server 2008 R2 is the release version
  44. Checks whether Simple Mail Transfer Protocol (SMTP) is installed
  45. Checks whether there are empty Servers containers
  46. Checks whether the accepted domain for Exchange is not the default domain
  47. Checks whether the application pool for SharePoint uses the default account
  48. Checks whether the application pool for SharePoint uses the default version of the .NET Framework
  49. Checks whether the application pool for SharePoint uses the default Managed Pipeline Mode
  50. Checks whether the application pool for SharePoint uses the default bit version
  51. Checks whether the application pool for PowerShell uses the default account
  52. Checks whether the application pool for PowerShell uses the default version of the .NET Framework
  53. Checks whether the application pool for PowerShell uses the default Managed Pipeline Mode
  54. Checks whether the application pool for PowerShell uses the default bit version

Patching related info from the Excel blog:

Patching related info from the Excel blog:


http://blogs.technet.com/b/the_microsoft_excel_support_team_blog/archive/2011/09/29/office-file-validation-causes-slow-opening-of-excel-files-from-network.aspx


http://blogs.technet.com/b/the_microsoft_excel_support_team_blog/archive/2011/09/28/links-in-excel-are-broken-after-applying-security-update-ms11-072.aspx


If you are seeing that second one, can you call into Microsoft?  They need repros in order to fix things and when they don’t have repros, they can’t fix.

Update Rollup 5 for Exchange Server 2010 Service Pack 1 (KB2582113)

On WSUS and MU tonight —


Other Updates Update Rollup 5 for Exchange Server 2010 Service Pack 1 (KB2582113)
This update rollup resolves problems that were found in Exchange Server 2010 Service Pack 1 (SP1) since Exchange Server 2010 SP1 was released and replaces previously released update rollups for Exchange Server 2010 SP1.


http://blogs.technet.com/b/exchange/archive/2011/08/23/released-update-rollup-5-for-exchange-2010-sp1.aspx


Remember that it’s normal for update rollups for Exchange to disable the serivces of Exchange and then restart them. After the rollup, go back and check the Exchange services to ensure that they are running after the update is installed.

Troubleshooting Client Connector Install : SBS2011 Essentials

Continuing on our recap of issues you might see installing the client connector to SBS essentials, Robert Pearman has recapped a wonderful and detailed list of everything we’ve seen so far in regards to crusty workstations and issues installing the client connector software.


http://titlerequired.com/2011/09/27/troubleshooting-client-connector-install-sbs2011-essentials/


Check it out there!


(and I think I should be afraid that he’s threatened my home address ;-)

Cannot connect the computer to the server – the computer has a restart pending

Installing a SBS Essentials to a Windows 7 and the log file pointed to a pending file rename issues….but… there was nothing in the registry keys.



(remember on Windows 7 the logs files you need to look at are in a hidden file in C:\ProgramData\Microsoft\Windows Server\Logs in XP they are located at  C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Server\Logs .)


The log file pointed to a registry key


09/24/2011 22:44:59 1af0] CSetup::RunTasks: Running Task: Id=-1 Description=Check Pending Reboot Index=  2
[09/24/2011 22:44:59 1af0] TaskCheckPendingReboot::Run – Regkey value PendingFileRenameOperations under [SYSTEM\CurrentControlSet\Control\Session Manager] is not empty.
[09/24/2011 22:44:59 1af0] CSetup::RunTasks: Task Id=-1 Description=Check Pending Reboot Failed
[09/24/2011 22:44:59 1af0] CSetup::Run: Failed to Run Verification Tasks
[09/24/2011 22:44:59 1034] CSetup::RunTasksDlgProc: Unxexpected or Fatal Error Occured
[09/24/2011 22:44:59 1034] CSetup::SetupErrorDlgProc: IDD_PROPPAGE_SETUP_ERR Initialization


But nothing was there



 Thanks to this thread (http://social.microsoft.com/Forums/en-IE/whs2011/thread/bac7d989-545f-4471-b4bb-173b82613934)

I was pointed to this vbs, stuck it in notepad, ran the vbs file and voila…that’s what the Colorado connector client software is getting stuck on.
http://blogs.msdn.com/b/tommills/archive/2008/08/15/a-handy-wmi-script-for-checking-for-pending-file-rename-operations.aspx



Lovely HP printer driver sticking itself in the pending file location.

I flipped the print spooler to manual, copied that folder to another location, rebooted the workstation and it FINALLY connected.

The log file kept pointing to the pending rename registry key but nothing was there.  This wmi script was the only thing that pointed me in exactly the proper direction of my problem.  After I got it connected I stopped the spooler again and moved the folder back.  Obviously sucky HP printer drivers were the problem.


I’ve attached the vbs file as a zip file to this blog post, extract it out and launch an admistrative command prompt and run that vbs script.  It should tell you what is getting stuck if it’s not obvious from the registry key.

When the log files give you a clue

I was installing a SBS Essentials and kept getting an error indicating a problem connecting the computer wouldn’t do a trust connection to the server.


http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver2011essentials/thread/90b907e8-6936-4140-b927-6d1ee14ef05c


In digging out the log files (per http://social.technet.microsoft.com/wiki/contents/articles/3887.aspx)


On XP machines the log files are located in C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Server\Logs and on Vista and later under the hidden ProgramData folder.


[1068] 110924.220212.0677: ClientSetup: JoinNetwork had errors: ErrorCatalog:CAError ErrorCode:2
BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetCert
at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetCert(String serverName, String userName, String password, Boolean bForce)
at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.JoinNetworkTask.Run(WizData data)
[1068] 110924.220212.0677: ClientSetup: Exiting JoinNetworkTask.Run


All the known resolutions talked about machine key permissions (which were set right in my case) or a time situationi on the workstations (also set fine in my case).  It wasn’t until I opened up the Certificate Authority on the server and remembered that I had shifted the date on the server because it wasn’t coming up with the right date… and sure enough after I shifted it back, the workstations installed just fine.


It was in looking at the CA and the failed cert deployments that it reminded me of a sequence that occurred in the deployment that might explain this.



The server was accidentally off in it’s time.  Bottom line this isn’t something that you’d normally see, but just remember to look in unexpected places like the Certificate Authority on a SBS Essentials box that might give you a clue of what’s going on.

Task scheduler failure causes issues installing Home Server 2011, SBS Essentials and Storage Server connector.

I’m trying to install a connector software on a Windows 7 machine and it’s not working.  And it looking around the issues people are hitting I’m going to recap some of the more interesting ones here:


Task scheduler failure causes issues installing Home Server 2011, SBS Essentials and Storage Server connector.


http://social.microsoft.com/Forums/en-US/whs2011/thread/624ebef2-ab1e-421e-9f4f-688b02cd62b8/


First off I would like to thank sbs_sdet_w and Xioafeng for helping me with this. I give them credit for steering me in the right direction but I’m marking this as answer because it explains how to fix it.


I don’t know if this fix will work for everyone, but I sure hope it does because it’ll make you pull your hair out if you can’t figure it out. This fix should work for SBS Essentials 2011 and WHS 2011. They are both about the same and considering the logs on here are from SBS Essentials 2011 and it worked, it should also work on WHS 2011

The main problem with this was caused by the security permissions for task scheduler being corrupted. If you see these lines at the bottom of yourclientdeploy.log:

 

“[644] 110802.131926.8092: ClientSetup: Running MSI: C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi SOFTWARE_NAME=”Windows Small Business Server 2011″ REBOOT=ReallySuppress
[644] 110802.132447.3678: ClientSetup: Running MSI threw an exception:Microsoft.Deployment.WindowsInstaller.InstallerException: Fatal error during installation.
at Microsoft.Deployment.WindowsInstaller.Installer.CheckInstallResult(UInt32 ret)
at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Helper.RunMsi(String msiPathOrProductCode, String logFilePath, Dictionary`2 msiProperties, Boolean install, ProgressChangedEventHandler progressHandler)
[644] 110802.132447.3678: ClientSetup: RunMsi returned error: RetCode=1603
[644] 110802.132447.3678: ClientSetup: Failed to install C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi
[644] 110802.132447.3678: ClientSetup: Exting InstallSoftwareTask.Run
[644] 110802.132447.3678: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has TaskStatus=Failed

[644] 110802.132447.3678: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has RebootStatus=NoReboot
[644] 110802.132447.3678: ClientSetup: Exting ConnectorWizardForm.RunTasks
[1740] 110802.132503.2127: ClientSetup: Back from the Client Deployment Wizard
[1740] 110802.132503.2127: ClientSetup: Saving Wizard Data
[1740] 110802.132503.2284: ClientSetup: End of ClientDeploy: ErrorCode=1603″

 

This is what prevented Launchpad from installing. None of the other errors I posted on here were related to the problem as they were still present in the logs after I had a successful install of Launchpad.

To fix this do the following.

First you need to see if task scheduler is running properly. Use this link provided bysbs_sdet_w to set it up if you don’t know how http://support.microsoft.com/kb/308569
Just pick any old task to run. I used disk cleanup and set it to run once. When you run it if you get the error“Task Scheduler error,0x80090016,Keyset does not exist” you just do this next.

  1. Stop the Task Scheduler Service (run => services.msc)
  2. Delete or Move ( I created a new folder and dumped them in there) the file(s) from the
    “C:Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA-S-1-5-18″ folder.
  3. Start the Task Scheduler Service.
  4. Edit each previously scheduled task and provide security credentials( It’ll as you for your login) for the task to run under.
  5. Right click a task and choose run.

The task should run correctly and it should also run as scheduled.

If task scheduler works you should be able to reinstall Launchpad with no problems now. If you haven’t cleaned out your old installation of Launched do it before you reinstall.
If you haven’t done that before do the following.

1. Remove the clients computer from the Server and restart it.
2. On the clients computer itself, go to Control Panel- System- Computer Name and clickChange.
3. On this tab change the computers name to anything you want to name it as long as it’s different from the one that is already there.
4. Change Domain to Workgroup and use the name of the Workgroup you belonged to before. If not, just putAnything.
5. Click OK, You’re Login screen should appear, Type in your login for the computer and then follow the on screen instructions to finish.
6. After the computer finishes rebooting run a good cleaner likeCCleaner. Run the file cleaner and the registry cleaner. This gets enough of
the old files out to reinstall Launchpad.

After that, reinstall the Launchpad software and you should be good to go. I didn’t have to uninstall .net 4.0 or turn off my antivirus software. But if you don’t want to take any chances of it screwing up again, shut off anything running in the background just to be sure.

This is all I did and it worked well for me. Some of your experiences may be different. If I missed anything please feel free to post here and correct it. If you are having this problem, I hope this works for you.

Thanks

Installing that connector software

When you start installing the connector software from SBS Essentials on your clients, one of the things you might want to bookmark is this wiki page: http://social.technet.microsoft.com/wiki/contents/articles/3887.aspx that gives you tips of different client connector installation issues we’ve seen so far.

Are you aware?

Are you aware of this VOIP vendor?  Check it out.


http://www.3cx.com/blog/voip-nuggets/installation-intro/