Search This Blog

Friday, March 25, 2016

Cannot obtain read/write access for install.wim

In some situations ICD can not do what you need, and because of that, you might still need a good old unattend.xml for Windows 10.

When opening a new install.wim in Windows System Image manager for the first time without a catalog file you will be asked if you want to create a new:

The catalog file for Windows 10 Enterprise Technical Preview cannot be opened for the following reason:

Cannot find the catalog file associated with the Window image Windows 10 Enterprise Technical Preview.

You must have a valid catalog file to continue. Do you want to create a catalog file?"

Technical Preview Smile https://twitter.com/mniehaus/status/666732194807742464

image

But when you answer Yes you might see this error:

Cannot obtain read/write access for install.wim.

In order to generate a catalog file, you must have read/write access to The Windows image file and its containing folder.

image

One explanation could be that the Install.wim is set to read-only, remove the Read-only mark and try again.

image

And the catalog file is now generated:

image

Thursday, March 17, 2016

Hi - We’re happy you’re here

When you logon to Windows 10 for the first time with a new user without a profile you will see this dialog:

Hi

 image

We’re happy you’re here

image

Lots of great features to get excited about

image

Getting everything ready for you

image

Let’s start

image

You might not like this dialog and prefer not to see it. setting the Group policy

Computer Configuration\Administrative Templates\System\Logon\Show first sign-in animation to disabled

image

Will change the dialog to this simple one (Preparing Windows):

image

You can also set this in unattened.xml as shown here:

image

    <settings pass="specialize">
        <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="
http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System /v EnableFirstLogonAnimation /t REG_DWORD /d 0 /f</Path>
                    <Order>2</Order>
                    <Description>Do not Show First Logon Animation</Description>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>
    </settings>

Or directly in your task sequence with the command

reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System /v EnableFirstLogonAnimation /t REG_DWORD /d 0 /f

Wednesday, March 9, 2016

SCCM client will not initialize during task Sequence

When using a custom Windows 10 1511 image captured with a SCCM 1511 client you might see that the step Setup Windows and Configuration manager will hang with the status Initializing the System Center Configuration manager client.

image

I you take a closer look at smsts.log you will see the message Waiting for CcmExec service to be fully operational.

image

According to Microsoft Connect this is a known bug and it will be fixed in the upcoming 16xx update.

Until then a workaround is to execute c:\windows\ccm\ccmrepair.exe right after Setup Windows and Configuration Manager step, and then add a reboot as shown here:

This can be done in the Build & Capture Task Sequence.

image

Wednesday, March 2, 2016

Has SCCM 2012 R2 SP1 CU3 been installed?

Cumulative Update 3 for System Center Configuration Manager 2012 R2 SP1 has been released https://support.microsoft.com/en-us/kb/3135680,

and if not already on System Center Configuration Manager (Current Branch) lets take a closer look at how to determine the installation status of this cumulative update:

image

Remember that you will only see the prompt about Automatic Client Update if you have automatic client upgrade feature is enabled.

image

image

Read more about Automatic Client Update her Automatically updating the Configuration Manager client

After upgrading to System Center Configuration Manager 2012 R2 SP1 CU3, you will be able to identify the update as shown here.

First let us take a look at the console, after the update the console reports version 5.0.8239.1403

image

The console reported version 5.0.8239.1301 before updating which is 2012 R2 SP1 CU2.

image

The Console update is also listed in Control Panel as an Installed Update.

image

The site will still report version 5.00.8239.1000 after the update (Also shown after the console version in above pictures).

image

In order to check if the update has been applied we must look in the registry.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup\CULevel

CULevel reports 3 after CU3 has been applied.
image

Before updating CULevel reported 2 because Cumulative Update 2 was installed.

image

This update is also visible under Installed Updates in Control Panel.

image

The client will report 5.00.8239.1403 after it has been updated.

image

With these components updated:

image

Before updating the client reported 5.00.8239.1301 for a 2012 R2 SP1 CU2 client:

image

CU2 includes the same update for SCEP as CU1 and CU2.

See Has SCCM 2012 R2 SP1 CU1 been installed?

All SCEP client should never the less be at version 4.8.204.0 from may 2015.

http://larslohmann.blogspot.dk/2015/07/system-center-endpoint-protection.html

https://support.microsoft.com/en-us/kb/3049560

image

Finally be aware of this statement from the support page:

After this cumulative update is installed on site servers, any operating system boot image should be updated!