Microsoft Error Codes seen during SCCM software deployments

I may have posted this before - I can't remember.

Error code               Value  Description
---------------------------------------------------------------------------
ERROR_SUCCESS               0   Action completed successfully.
ERROR_INVALID_DATA         13   The data is invalid.
ERROR_INVALID_PARAMETER    87   One of the parameters was invalid.
ERROR_INSTALL_SERVICE_
 FAILURE                 1601   The Windows Installer service could not be 
                                accessed. Contact your support personnel 
                                to verify that the Windows Installer 
                                service is properly registered.
ERROR_INSTALL_USEREXIT   1602   User cancel installation.
ERROR_INSTALL_FAILURE    1603   Fatal error during installation.
ERROR_INSTALL_SUSPEND    1604   Installation suspended, incomplete.
ERROR_UNKNOWN_PRODUCT    1605   This action is only valid for products that
                                are currently installed.
ERROR_UNKNOWN_FEATURE    1606   Feature ID not registered.
ERROR_UNKNOWN_COMPONENT  1607   Component ID not registered.
ERROR_UNKNOWN_PROPERTY   1608   Unknown property.
ERROR_INVALID_HANDLE_
 STATE                   1609   Handle is in an invalid state.
ERROR_BAD_CONFIGURATION  1610   The configuration data for this product is 
                                corrupt. Contact your support personnel.
ERROR_INDEX_ABSENT       1611   Component qualifier not present.
ERROR_INSTALL_SOURCE_
 ABSENT                  1612   The installation source for this product 
                                is not available. Verify that the source 
                                exists and that you can access it.
ERROR_INSTALL_PACKAGE_
 VERSION                 1613   This installation package cannot be 
                                installed by the Windows Installer 
                                service. You must install a Windows 
                                service pack that contains a newer version 
                                of the Windows Installer service.
ERROR_PRODUCT_
 UNINSTALLED             1614   Product is uninstalled.
ERROR_BAD_QUERY_SYNTAX   1615   SQL query syntax invalid or unsupported.
ERROR_INVALID_FIELD      1616   Record field does not exist.

ERROR_INSTALL_ALREADY_
 RUNNING                 1618   Another installation is already in 
                                progress. Complete that installation 
                                before proceeding with this install.
ERROR_INSTALL_PACKAGE_
 OPEN_FAILED             1619   This installation package could not be 
                                opened. Verify that the package exists and 
                                that you can access it, or contact the 
                                application vendor to verify that this is 
                                a valid Windows Installer package.
ERROR_INSTALL_PACKAGE_
 INVALID                 1620   This installation package could not be 
                                opened. Contact the application vendor to 
                                verify that this is a valid Windows 
                                Installer package.
ERROR_INSTALL_UI_
 FAILURE                 1621   There was an error starting the Windows 
                                Installer service user interface. Contact 
                                your support personnel.
ERROR_INSTALL_LOG_
 FAILURE                 1622   Error opening installation log file. 
                                Verify that the specified log file 
                                location exists and is writable.
ERROR_INSTALL_LANGUAGE_
 UNSUPPORTED             1623   This language of this installation package 
                                is not supported by your system.
ERROR_INSTALL_TRANSFORM_
  FAILURE                1624   Error applying transforms. Verify that
                                the specified transform paths are valid.
ERROR_INSTALL_PACKAGE_
 REJECTED                1625   This installation is forbidden by system 
                                policy. Contact your system administrator.
ERROR_FUNCTION_NOT_
 CALLED                  1626   Function could not be executed.
ERROR_FUNCTION_FAILED    1627   Function failed during execution.
ERROR_INVALID_TABLE      1628   Invalid or unknown table specified.
ERROR_DATATYPE_MISMATCH  1629   Data supplied is of wrong type.
ERROR_UNSUPPORTED_TYPE   1630   Data of this type is not supported.
ERROR_CREATE_FAILED      1631   The Windows Installer service failed to 
                                start. Contact your support personnel.
ERROR_INSTALL_TEMP_
 UNWRITABLE              1632   The temp folder is either full or 
                                inaccessible. Verify that the temp folder 
                                exists and that you can write to it.
ERROR_INSTALL_PLATFORM_
 UNSUPPORTED             1633   This installation package is not supported 
                                on this platform. Contact your application 
                                vendor.
ERROR_INSTALL_NOTUSED    1634   Component not used on this machine.
ERROR_PATCH_PACKAGE_
 OPEN_FAILED             1635   This patch package could not be opened. 
                                Verify that the patch package exists and 
                                that you can access it, or contact the 
                                application vendor to verify that this is 
                                a valid Windows Installer patch package.
ERROR_PATCH_PACKAGE_
 INVALID                 1636   This patch package could not be opened. 
                                Contact the application vendor to verify 
                                that this is a valid Windows Installer 
                                patch package.
ERROR_PATCH_PACKAGE_
 UNSUPPORTED             1637   This patch package cannot be processed by 
                                the Windows Installer service. You must 
                                install a Windows service pack that 
                                contains a newer version of the Windows 
                                Installer service.
ERROR_PRODUCT_VERSION    1638   Another version of this product is already 
                                installed. Installation of this version 
                                cannot continue. To configure or remove 
                                the existing version of this product, use 
                                Add/Remove Programs on the Control Panel.
ERROR_INVALID_COMMAND_
 LINE                    1639   Invalid command line argument. Consult the 
                                Windows Installer SDK for detailed command 
                                line help.
ERROR_INSTALL_REMOTE_
  DISALLOWED             1640   Installation from a Terminal Server
                                client session not permitted for 
                                current user.
ERROR_SUCCESS_REBOOT_
  INITIATED              1641   The installer has started a reboot.
                                This error code not available 
                                on Windows Installer version 1.0.
ERROR_PATCH_TARGET_
  NOT_FOUND              1642   The installer cannot install the
                                upgrade patch because the program
                                being upgraded may be missing, or the
                                upgrade patch updates a different
                                version of the program. Verify that 
                                the program to be upgraded exists on
                                your computer and that you have the 
                                correct upgrade patch.
 
                                This error code is not available on
                                Windows Installer version 1.0.
ERROR_SUCCESS_REBOOT_
 REQUIRED                3010   A restart is required to complete the 
                                install. This does not include installs 
                                where the ForceReboot action is run. Note 
                                that this error will not be available until 
                                future version of the installer. 
    

Creating a Windows 2 Go USB device

So our IT Director managed to break his Windows 2 Go (W2G) pen I created for him a few months back.  I kicked myself that I hadn't blogged the steps back then so as I've had to recreate it I'm taking the opportunity to blog it now.

The Windows 8 W2G GUI didn't let me see my .wim - I'm guessing this is due to the size of it.  I opted to build it via Powershell which worked a charm.

I used a Windows8 wim that I'd captured from our corporate build - I already have this so this is one of my assumptions that you will have it too.

I also have an approved Windows 2 Go USB pen (Kingston DataTraveler Workspace 32GB)

These are the devices currently supported by Microsoft:

• IronKey Workspace W300 (http://www.ironkey.com/wtg)
• Kingston DataTraveler Workspace for Windows To Go (http://www.kingston.com/wtg/)
• Spyrus Portable Workplace (http://www.spyruswtg.com/)
  We recommend that you run the Spyrus Deployment Suite for Windows To Go to provision the Spyrus Portable Workplace.
• Spyrus Secure Portable Workplace (http://www.spyruswtg.com/)
  

  Important
  You must use the Spyrus Deployment Suite for Windows To Go to provision the Spyrus Secure Portable Workplace. For more information about the Spyrus Deployment Suite for Windows To Go please refer to http://www.spyruswtg.com/.

• Super Talent Express RC4 for Windows To Go
  Super Talent Express RC8 for Windows To Go
  (http://www.supertalent.com/wtg/)
• Western Digital My Passport Enterprise (http://www.wd.com/wtg)

Also you will need to change your BIOS boot order to boot to USB first.

Instructions

Assumptions:

• You already have Windows 8 image (.wim) file - OOTB or captured.
• You have an approved USB device from the list above.

1. From a Windows 8 machine fire up an elevated Powershell prompt.
2. The following commands will prepare your USB device to be used with W2G.  Type them in the Powershell window:

#The following command will set $Disk to all USB drives with >20 GB of storage

$Disk = Get-Disk | Where-Object {$_.Path -match "USBSTOR" -and $_.Size -gt 20Gb -and -not $_.IsBoot }

#Clear the disk. This will delete any data on the disk. (and will fail if the disk is not yet initialized. If that happens, simply continue with ‘New-Partition…) Validate that this is the correct disk that you want to completely erase.

#

# To skip the confirmation prompt, append –confirm:$False

Clear-Disk –InputObject $Disk[0] -RemoveData

# This command initializes a new MBR disk

Initialize-Disk –InputObject $Disk[0] -PartitionStyle MBR

# This command creates a 350 MB system partition

$SystemPartition = New-Partition –InputObject $Disk[0] -Size (350MB) -IsActive

# This formats the volume with a FAT32 Filesystem

# To skip the confirmation dialog, append –Confirm:$False

Format-Volume -NewFileSystemLabel "UFD-System" -FileSystem FAT32 `

-Partition $SystemPartition

# This command creates the Windows volume using the maximum space available on the drive. The Windows To Go drive should not be used for other file storage.

$OSPartition = New-Partition –InputObject $Disk[0] -UseMaximumSize

Format-Volume -NewFileSystemLabel "UFD-Windows" -FileSystem NTFS `

-Partition $OSPartition

# This command assigns drive letters to the new drive, the drive letters chosen should not already be in use.

Set-Partition -InputObject $SystemPartition -NewDriveLetter "S"

Set-Partition -InputObject $OSPartition -NewDriveLetter "W"

# This command toggles the NODEFAULTDRIVELETTER flag on the partition which

prevents drive letters being assigned to either partition when inserted into a different machine.

Set-Partition -InputObject $OSPartition -NoDefaultDriveLetter $TRUE

3. Now we need that Windows 8 image.  For the sake of this example we'll say the image is on C:\ and it's called windows8.wim.
We will use DISM (Deployment Image Servicing Management) to aplpy the image to the USB drive - it could take 30 mins or longer so time to sti back and enjoy a brew...

dism /apply-image /imagefile:c:\windows8.wim /index:1 /applydir:W:\

4. Now we will use BCDBOOT to move the boot componants to the sys partition.

W:\Windows\System32\bcdboot W:\Windows /f ALL /s S:

5. To prevent the native HDD from being fired up whilst within W2G we need a policy in place.  Here's one I prepared earlier - copy the san_policy.xml file to the root of your USB device: http://sdrv.ms/149ZHV1

6. Apply the policy file we just created by running this command:

Dism.exe /Image:W:\ /Apply-Unattend:W:\san_policy.xml

7. Create an answer file (unattend.xml) that disables the use of Windows Recovery Environment with Windows To Go. You can use the code from the sample here to create a new answer file or you can paste it into an existing answer file (or just use the file itself):

8. Once the answer file has been saved, copy unattend.xml into the sysprep folder on the Windows To Go drive (for example, W:\Windows\System32\sysprep\)

Note

Setup unattend files are processed based on their location. Setup will place a temporary unattend file into the %systemroot%\panther folder which is the first location that setup will check for installation information.  You should make sure that folder does not contain a previous version of an unattend.xml file to ensure that the one you just created is used.


Now boot to your new shiney Windows2Go boot device :)

docN

Windows Blue officially named "Windows 8.1" - and it's free!

 

So after much deliberation and hearsay Microsoft have announced that Windows "Blue" will be officially released as Windows 8.1 - and IT WILL be free!

Release dates so far have been speculated as "later this year" but there are indications that it could be ready for the holidays.

This task sequence cannot be run because a package referenced by the task sequence could not be found.

If like me you have been bashing your head against many firewalls during Windows 7 OSD via SCCM you will probably sometime come across the error:

This task sequence cannot be run because a package referenced by the task sequence could not be found.

More annoyingly it doesn't reference the guilty package in the onscreen error.  After checking the many log files CCM generates I found within the RAM drive path: x:\windows\temp\SMSTSLog resides the relevent SMSTS.LOG file.

The full error I recieved was after selecting the relevant OSD TS; resolving polices and then BAM :

This task sequence cannot be run because a package referenced by the task sequence could not be found. For more information, please contact your system administrator or helpdesk operator.

I also noticed (and please use SMS Trace to view error logs):

Failed to find CCM_SoftwareDistribution object for AdvertID="xxx", PackageID="xxx", ProgramID="*"

I found it was a Lenovo Graphics Driver Package causing the issue; it appears SCCM has yet another little "quirk" where the hash isn't written sometimes upon creation of a package and the initial ditribution.  If the version number of the guilty package is "1" try right clicking on the DP of the package and select "Update Distribution Points".

After some time the Source Version will increment to "2" and the date will be current - give your OSD another try and then see if it works - if it fails - check the log file again as this time the guilty package may have changed and it may be a case of trawling through a few before you resolve the issue.

I hope this helps.

Many thanks to J over at ManagedUX for the pointer!

Training Ahoy!

Finally it looks like I will be undergoing some SCCM training.  My employer have agreed to send me on Microsoft's M6451 "Planning, Deploying and Managing Microsoft System Center Configuration Manager 2007" at QA in Manchester.

This is what I have wanted to do for a while now - hopefully I can do the 70-401 exam soon enough and get my MSTS!

Configuring Windows 8 Dev on Virtual Box in 10 simple steps...

With the release of Tiny Flaccid's Windows 8 Developer Preview there are tons of geeks and demi geeks out there just bursting to give it a try.  Ironically it will not work with their own flavor of VM so here's another way to try getting your shiny shiny fix for today!

Assumptions:

• You have the latest version of VBox
• You have downloaded the W8Dev .iso - I used 32bit.
• PC Supports hardware virtualisation

1. So from VBox we knock out a new VM.
2. Under Motherboard tab in system tick IO APIC
3. Under Processor enable PAE/NX
4. Under Acceleration tick Enable VT-x/AMD-v and also Enable Nested Paging
5. Under Display - Video tick Enable 2D Acceleration
6. Under Storage click the CD icon under IDE Controller and choose IDE Primary Slave
7. Click the CD icon to the right of this and choose a virtual CD/DVD disk file - point to your ISO
8. Click OK
9. Click Start
10. Hey Presto - it works!!!

If it doesn't - I don't know!!!