Feb 14
Windows 8
icon1 Trace | icon2 Technical | icon4 02 14th, 2012| icon3No Comments »

I got to play around with Microsoft Windows 8 client with Metro on a few devices. This new OS from Microsoft seems to have a very few improvements over Windows 7. There is new dashboard type interface that appears to be focused on touch devices. In all honesty this seems to be the only improvement of note.

The touch interface is good. The soft keyboard performed well. The interface was easy to navigate and intuitive. I found the use for it to be mostly eye candy though. Anytime you opened a useful application you were taken back over to a Windows 7 feeling desktop. I looked inside regedit and control panel, I found nothing really new here. In fact many things looked exactly like Windows 7.

The lack of finding anything really different in the desktop side of Windows 8 has lead me to believe that maybe Metro was just a skin on Windows. As I later discovered, Metro is in fact not just a skin on Windows 8. The Internet Explorer appears to run in a separate space on Metro vs. the desktop.

I asked myself, what is the benefit of Windows 8 to the average corporate worker in an office? The answer is nothing. The real benefits are for mobile workers and those who wish to consume Windows 8 with a touch device. I could easily see using an iPad or other touch device to consume a Windows 8 virtual desktop with ease. This of course would depend on the swipe and other touch capabilities working via remote desktop.

There are a few other remote worker beneficial technologies in Windows 8. As I discover their real benefits in the future I am sure we will discuss them. For now I am anxiously awaiting the release of Windows 8 client for use in the home.


Aug 24

When using Outlook 2007 with Exchange 2007 some of our users would get prompted to login to the client access server. Clicking cancel would still allow them in their mailbox with what appeared to be all functionality. However the prompt would return after a few minutes. This was very annoying as you can imagine. After some web searching I was able to find the problem a long with a solution.

First open up Exchange 2007 powershell. We’ll check on the problem and verify it is the same as well as fix it from here.

Run the following command.
[PS] C:\Windows\System32>Get-ClientAccessServer | fl

Name : EXCH03
OutlookAnywhereEnabled : False
AutoDiscoverServiceCN : exch03
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://exch03.company.com/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {DownTown}
IsValid : True
OriginatingServer : ADDC01.company.com
ExchangeVersion : 0.1 (8.0.535.0)
DistinguishedName : CN=EXCH03,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administ
rative Groups,CN=PHE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,D
C=com
Identity : EXCH03
Guid : 341169c4-dd14-47b2-b3e6-01ca8653dfbb
ObjectCategory : company.com/Configuration/Schema/ms-Exch-Exchange-Server
ObjectClass : {top, server, msExchExchangeServer}
WhenChanged : 4/22/2009 10:03:06 AM
WhenCreated : 4/7/2009 10:37:52 AM


Name : EXCH04
OutlookAnywhereEnabled : False
AutoDiscoverServiceCN : EXCH04
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://mail.company.com/autodiscover/autodiscover.xml
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {DownTown}
IsValid : True
OriginatingServer : ADDC01.company.com
ExchangeVersion : 0.1 (8.0.535.0)
DistinguishedName : CN=EXCH04,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administ
rative Groups,CN=PHE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,D
C=com
Identity : EXCH04
Guid : 4857fd2e-da32-4a7c-a97a-cfb0135d2875
ObjectCategory : company.com/Configuration/Schema/ms-Exch-Exchange-Server
ObjectClass : {top, server, msExchExchangeServer}
WhenChanged : 4/13/2009 12:46:00 PM
WhenCreated : 4/13/2009 10:07:00 AM

You should notice here that our AutoDiscoverServiceInternalUri points to our external dns name for Outlook Web Access. This is our problem. This should be the internal dns name for our client access server. Here is the command to set it to what we want.

[PS] C:\Windows\System32>Set-ClientAccessServer -Identity "EXCH04" -AutodiscoverServiceInternalURI "https://exch04
.company.com/Autodiscover/Autodiscover.xml"
[PS] C:\Windows\System32>


Mar 18

If you have an Enterprise Agreement or Volume License from Microsoft you may wish to bookmark this one. When downloading SQL 2005 Standard or Express you have 2 iso’s to download. One has a #1 in the name and the other #2 in the name. Grab them both. The first is the servers install and the second is the tools. If you happen to only get the first, you will soon learn you cannot install the management consoles and other client connectivity options. Oh sure the setup will allow you to select them. You’ll even get the installation to kick off and run a bit. But rest assured by the time you get back from lunch your install will have failed. You’ll see a message like:

    There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.

You can go and double check your logs to make sure it is the same issue. Check the logs here:

    C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files

If it turns out to be the same issue you should see something like the following:

Running: InstallToolsAction.10 at: 2006/4/8 16:46:2
Error: Action "InstallToolsAction.10" threw an exception during execution. Error information reported during run:
Target collection includes the local machine.
Fatal Exception caught while installing package: "10"
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified. Source File Name: sqlchaining\sqlprereqpackagemutator.cpp
Compiler Timestamp: Tue Aug 9 01:14:20 2005
Function Name: sqls::SqlPreReqPackageMutator::modifyRequest
Source Line Number: 196
---- Context -----------------------------------------------
sqls::InstallPackageAction::perform
WinException caught while installing package. : 1603
Error Code: 0x80070643 (1603)
Windows Error Text: Fatal error during installation. Source File Name: packageengine\installpackageaction.cpp
Compiler Timestamp: Fri Jul 1 01:28:25 2005
Function Name: sqls::InstallPackageAction::perform
Source Line Number: 167
---- Context -----------------------------------------------
sqls::InstallPackageAction::perform

If everything checks out this far then here is how to fix it. You need #1 and #2 iso’s. Extract #1 to *:\sql2005\servers. Then extract #2 to *:\sql2005\tools. Now rerun your setup from the servers directory. Now when you select to install servers and client components etc it will successfully install.

Source I used to fix my problem the first time.

http://support.microsoft.com/kb/916760/en-us