Table of contents
TOC
Collapse the table of content
Expand the table of content

Known Issues and Limitations

JuanPablo Jofre|Last Updated: 10/14/2016
|
2 Contributors

PowerShell Shortcuts are broken when used for the first time

Resolution: Perform one of the following actions:

  1. Right click on the PowerShell shortcut. Select “Windows PowerShell” to launch in a non-elevated mode.
  2. Right click on the PowerShell shortcut. Right click on “Windows PowerShell” and select “Run As Administrator” to launch in an elevated mode.

Once you have performed either of the above actions, the PowerShell shortcuts will work. These actions need to be performed only once.

PowerShell Modules and DSC Resources report errors about ExecutionPolicy on Windows 7

On Windows 7, the use of PowerShell modules and DSC resources may result in errors reported about ExecutionPolicy.

Resolution: Set the ExecutionPolicy to RemoteSigned by running the following command in an elevated PowerShell session (Run as Administrator):

Set-ExecutionPolicy RemoteSigned

Connecting to an old remote Exchange endpoint causes a crash

The old Exchange endpoint redirects to a new endpoint. There is a bug in the redirection logic that results in a crash.

Resolution: Connect directly to the new endpoint.

Software Inventory Logging feature is erroneously stopped after WMF 5.0 installation on Windows Server 2012 R2

When installing WMF 5.0 on a Windows Server 2012 R2 that is already running SIL, the Software Inventory Logging feature is erroneously stopped after installation.

Resolution: Run the Start-SilLogging cmdlet once after the WMF installation, as the installation process will errantly stop the Software Inventory Logging feature.

Get-ChildItem does not work if -LiteralPath and -Recurse are used together

If a directory name contains an invalid wildcard character, then Get-ChildItem will not produce expected results when both -LiteralPath and -Recurse are used together.

Resolution: Not ideal, but current workaround is to implement recursion in the script rather than rely on the cmdlet.

Sysprep fails after WMF 5.0 installation

There are two workarounds for this issue depending on the version of Windows Server you are running.

Resolution:

  • For systems running Windows Server 2008 R2

    1. Open Powershell as an administrator
    2. Run the following command
      Set-SilLogging –TargetUri https://BlankTarget –CertificateThumbprint 0123456789
    
    1. Run the command and ignore the error, as they are expected.
      Publish-SilData
    
    1. Delete the files in \Windows\System32\Logfiles\SIL\ directory
      Remove-Item -Recurse $env:SystemRoot\System32\Logfiles\SIL\
    
    1. Install all available important Windows Updates, and begin Sysyprep operation normally.
  • For systems running Windows Server 2012

    1. After installing WMF 5.0 on the server to be Sysprep’d, login as administrator.
    2. Copy Generize.xml from directory \Windows\System32\Sysprep\ActionFiles\ to a location outside of the Windows directory, C:\ for example.
    3. Open your Generalize.xml copy with notepad.
    4. Find and remove the following text, one instance of each needs to be deleted (they will be near the end of the document).

      <sysprepOrder order="0x3200"></sysprepOrder>
      <sysprepOrder order="0x3300"></sysprepOrder>
      
    5. Save the edited copy of Generalize.xml and close the file.

    6. Open a command prompt as administrator
    7. Run the following command to take ownership of the Generalize.xml file in system32 folder:

      Takeown /f C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml
      
    8. Run the following command to set appropriate permission on the file:

      Cacls C:\Windows\System32\ Sysprep\ActionFiles\Generalize.xml /G `<AdministratorUserName>`:F
      
      • Answer Yes at the prompt for confirmation.
      • Note that <AdministratorUserName> should be replaced by the username who is administrator on the machine. For example, "Administrator".
    9. Copy the file you edited and saved over to the Sysprep directory using the following command:

      xcopy C:\Generalize.xml C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml
      
      • Answer Yes to overwrite (note that if there is no prompt to overwrite, double check the path entered).
      • Assumes your edited copy of Generalize.xml was copied to C:\ .
    10. Generalize.xml is now updated with the workaround. Please run Sysprep with the generalize option enabled.

© 2017 Microsoft