Archive for August, 2011

You installed succesfull Windows 7 x86 on a Dell Latitude D420 and wondering why you can’t install the Dell Wireless 5530 HSPA modem? If you get the following error from Windows 7 after installing the card in your notebook then you shouldn’t leave.



The first thing you should do, is downloading the correct Windows 7 x86 driver. At the time of my download, it it was R243926. The installer will abort with the error 23000 Authentication Error, like the following screenshot.


You should not close the error message, instead you should look for the msi installer in the temp folder of you profile. The folder looks like {5497CED3-F71E-44B1-9308-D9A15048540D}. There you will see Dell Wireless HSPA Mini-Card Drivers.msi. Now download the ORCA software from Microsoft, which can be used to edit msi packages.

After that you should open the msi package and edit the table CustomAction and delete (here is called Drop Row) the Action Authenticate. Please don’t forget to save the msi package and copy it from your temp folder. Now you can close your error message and run the copied msi package.

Everything should be fine now.



Be Happy. Zwinkerndes Smiley


sneak peek – Windows Server “8”

Today I saw the sneak peek from Windows Server “8” with very great features.


  • 16 vCPUs per Guestmachines
  • image image

  • Hyper-V Storage Replication (asynchron)
  • image

    I am very excited about the new features.

    Looking forward to Windows Server “8”!!! Smiley mit geöffnetem Mund

    Our SCCM environment consists of a central site and a few primary child sites for each country. The buildin collections are only provided from out central site, so they are protected on each child site and can not be modified there.

    Today we created a new collection on a child site and linked an inherited collection (All Windows 7 Systems) to this new collection:


    As you can see, the collection is protected even if it’s only an instance, as in our case. If you now want to delete this instance you are not able to.

    We searched the web and found no solution for this bug and we believe that it is one. So we have to digg into the SCCM collection management and found a solution.

    Please be very careful if you try our solution, because a wrong handling may led to an inconsistent SCCM database. We don’t give any guarantee.

    1. Download the WMI Administrative Tools and install them on a client computer. We used a Windows XP computer.
    2. Start the WMI Object Browser, a part of the WMI Administrative Tools. The object browser starts in an internet explorer window and tries to connect to the default WMI namespace on the client computer:
    3. Connect to WMI namespace on your site server for the child site. Therefore klick on the small icon beside the selected namespace too browse to the SCCM site server you have the linked collection to be deleted, put in the site server name and as starting namespace use “root\sms” as shown:
                      wmi_object_browser_connect2 wmi_object_browser_connect3
      Klick on connect and put in appropriate credentials to connect to your site servers WMI. Select the namespace corresponding to your site code and klick ok. Now you have to specifiy the browser criteria which is the SMS_Collection class. Add it it and go further with ok:
      You get another window where you have to choose the collection which helds the collection link to be deleted.  
      In our case it was the collection “Manage” with the ID “BCG0004F” and if you go ahead with ok you can see all the properties of your collection.
    4. Temporarily unset the protected flag for the collection to be deleted. To do that, open the object tree as shown in the following picture and select the trouble making collection. In our case the collection with id “ABC00048”:
      After choosing this collection you can see properties for this collection on the site-server!!! This is important to think of!!!

      Change the property “OwnedByThisSite” from false to true, save your change with the disk icon (marked with the arrow) and refresh the collection tree in your configuration manager console. Now you are able to delete the instance of this collection, like with any other collection not inherited.

      When deleted you should set the property to false afterwards, to get not in trouble with the central site

    Again remember, the change we’ve made here was only for the child site, regarding a collection inherited from the central site!!!

    So please be very careful of what you are doing.