IT Consultant Everyday Notes

Just some problems/solutions storage

Monthly Archives: October 2013

WinPE: The following processor architecture was not found: amd64.

Problem:

I am trying to create a WinPE bootable flash drive for WinPE 4.0 provided by Windows Assessment and Deployment Kit 8.1

to prepare WinPE Source directory I navigate to “C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment” folder (default installation for ADK) and run

copype amd64 d:\WinPE_amd64

The installation fails with error:

ERROR: The following processor architecture was not found: amd64.

 

Resolution:

after digging copype.cmd I found that some variables are missing. I guess they were set up with older version of WAIK, when we had a chance to start “WAIK” command prompt; but now we (at least I) do not have this customized command prompt in Windows 8/8.1 and the variables are not set.

So, I added the variables manually and change a line in the batch file (copype.cmd)

Here are variables I added (there are two variables, each on its own line, depending on your installation path – mine are default):

set WinPERoot=C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment
set OSCDImgRoot=C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools

and I also changed FWFILESROOT line to:

set FWFILESROOT=%OSCDImgRoot%\%WINPE_ARCH%\Oscdimg    (I added a variable and removed “\..\..”)

At the end the changed part of copype.cmd looks like (changes are in red):

rem
rem Set environment variables for use in the script
rem
set WINPE_ARCH=%1
set WinPERoot=C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment
set OSCDImgRoot=C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools
set SOURCE=%WinPERoot%\%WINPE_ARCH%

set FWFILESROOT=%OSCDImgRoot%\%WINPE_ARCH%\Oscdimg
set DEST=%~2
set WIMSOURCEPATH=%SOURCE%\en-us\winpe.wim

After that I saved the changed copype.cmd and reran it – It generated source WinPE folder structure for me successfully.

Advertisements

SCSM: Self-Service Portal pages are blank

I installed a Self-Service Portal for SCSM, but all pages are blank (menu is there Smile )

It turned out be a certificate issue. In the test environment I created a self-signed cert using IIS Certificate Wizard. The Wizard created a certificate for FQDN, but in Application Settings SharePoint uses NETBIOS name of the server. As a result the Portal cannot connect to Content Web Server.

 

Resolution:

I believe there are several ways to resolve it:

Method one:   Create a self-signed cert for NETBIOS name of the server.

Method Two: Change Aplication Settings for Portal to match name of the Content server on its certificate (change it to FQDN if cert uses it)

image

Method three (I used): Issue a certificate with NetBIOS name of the server as CN and FQDN as SAN. Assign the certificate to both Portal web site and Web Content Web site.

Do not forget to restart web site after that (or IIS).

Good luck.

SCSM 2012 Data Warehouse Registration Failed

 

Tried to register Data Warehouse and got the abovementioned error.

 

Resolution:

1. Close the console

2. Run PowerShell as Administrator

3. Run:   Set-ExecutionPolicy RemoteSigned

4. Restart SCSM console and Re-register Data Warehouse Server

SCCM: Delete actions auditing