Search This Blog

Thursday, October 22, 2015

Install Software Updates fails in OSD

You might see this error when deploying Windows with SCCM 2012 R2 SP1, Task Sequence has failed with the error code (0x80004005)

image

When you look at the Installation Progress you will notice the the task sequence is installing updates and last status is Detecting Updates:

image

In smsts.log you will see that the step failed and that the Process completed with exit code 2147500037

image

One possible solution might be to take a closer look at your Software Update Deployment Packages, in this scenario one of the update packages was not available from any Distribution points.

image

After distributing the Deployment Package everything worked as expected.

Monday, October 12, 2015

Where to download Makecert.exe or Certmgr.exe?

You may need Makecert.exe or Certmgr.exe to deal with certificates, but where to download?

There are more than one way to get your hands on these files, but one way is to start a virtual Windows 8.1 client and install Windows Software Development KIT (SDK).

Go to the address https://msdn.microsoft.com/en-us/windows/desktop/bg162891.aspx and download the SDK installer.

image

After download start sdksetup

image

Note the default installation path and click Next:

image

Decide if you want to join CEIP:

image

Accept License Agreement:

image

Only install Windows Software Deployment Kit:

image

Wait for the installation to complete and close the installation confirmation:

image

You will find the files in the installation path:

C:\Program Files (x86)\Windows Kits\8.1\bin\x64 or C:\Program Files (x86)\Windows Kits\8.1\bin\x86 depending on the version you need:

image

You can copy the files from the virtual machine to use it on another computers, and after copying the files off the VM you can dispose the Virtual machine.

Makecert Documentation  Certmgr Documentation

And now your off to create a self signed certificate, export certificates and much more.

Friday, October 2, 2015

Some library features are unavailable due to unsupported library locations

You might see this warning on Windows 7, Windows 8, Windows 10 or when working with RDS/XenApp servers and libraries:

Some library features are unavailable due to unsupported library locations. click here to learn more.

Windows 7:

image

Windows 8.1:

image

And Windows 10:

image

You will see this warning if you have folders redirected to server shares that are not remotely indexed and cannot be synchronized offline and locally cached. This could for example be the case if you use 3. party external storage.

But if you use a Windows file server it could be because you don’t allow the redirected data to be available offline.

image

If you know the reason and you're not going to change it, you can disable the warning using a group policy setting.

Go to User Configuration – Policies – Administrative Templates – Windows Components – File Explorer - Turn off Windows Libraries features that rely on indexed file data and enable this policy:

image

This policy lets you turn off rich library functionality that depends on the availability of indexed file properties and contents. This Group Policy is intended to reduce user confusion and avoid frequent grep searches.

This policy disables:

  • Searching libraries in the Start menu
  • Applying Arrange By views other than “By Folder” and “Clear Changes”
  • Using Library Search Filter suggestions other than “Date Modified” and “Size”
  • Using the “Unsupported” tag in the Library Management dialog
  • Applying rich functionality to user-created Libraries
  • Viewing file content snippets in the “Content” view mode
  • Notifying users that unsupported locations are included in libraries

https://technet.microsoft.com/en-us/library/dd744697(WS.10).aspx#WS_TurnOffWindowsLibraries