• 07Oct

    IPv6 InterfaceIPv6 can cause some problems for applications that are not configured to use IPv6. By default IPv6 is enabled with Windows, disabling it can be tricky because even after you deselect Internet Protocol Version 6 (TCP/IPv6)” in the connection properties of your device it still doesn’t disable all IPv6 components. You can verify this by running ipconfig /all. Therefore to truly disable IPv6 you have to modify the following keys in the registry.

    In the Registry Editor, locate and then click the following registry subkey:


    REG_DWORD: 0xff

    Other value options you might want to consider are:

    0 to re-enable all IPv6 components (Windows default setting).
    0xff to disable all IPv6 components except the IPv6 loopback interface. This value also configures Windows to prefer using IPv4 over IPv6 by changing entries in the prefix policy table. For more information, see Source and destination address selection.
    0x20 to prefer IPv4 over IPv6 by changing entries in the prefix policy table.
    0x10 to disable IPv6 on all non-tunnel interfaces (both LAN and Point-to-Point Protocol [PPP] interfaces).
    0x01 to disable IPv6 on all tunnel interfaces. These include Intra-Site Automatic Tunnel Addressing Protocol (ISATAP), 6to4, and Teredo.
    0x11 to disable all IPv6 interfaces except for the IPv6 loopback interface.

    If you are trying to disable IPv6 completely I would recommend “0xff” because this value also configures windows to prefer IPv4 over IPv6.

    You can apply this setting via Group Policy or via command line:

    To Add:
    PS: New-Item -Type DWord -Path HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents -Value “0xff” -Force
    CMD: REG ADD HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters /v DisabledComponents /t REG_DWORD /d 0xff /f

    To Verify:
    PS: Test-Path -Path HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents
    CMD: REG QUERY HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters /v DisabledComponents

    After you’ve applied this key you must reboot the system for it to completely take effect.


    Ref: https://support2.microsoft.com/kb/929852

  • 06Oct

    The profile for the user is a temporary profile

    When installing an application you get this error message “The profile for the user is a temporary profile”. This happens after installing a security update: MS14-049. This update affects the execution process of the Windows Installer. To bypass this, set the following registry key and it will ignore this prompt and continue with the installation.


    REG_DWORD: 1

    You can apply this setting via Group Policy or via command line:

    To Add:
    PS: New-Item -Type DWord -Path HKLM:\SOFTWARE\Policies\Microsoft\Windows\Installer\SecureRepairPolicy -Value “1” -Force
    CMD: REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer /v SecureRepairPolicy /t REG_DWORD /d 1 /f

    To Verify:
    PS: Test-Path -Path HKLM:\SOFTWARE\Policies\Microsoft\Windows\Installer\SecureRepairPolicy
    CMD: REG QUERY HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer /v SecureRepairPolicy

    Another option is that you can add the software GUID’s to a whitelist reference is listed below.
    Ref: https://support2.microsoft.com/kb/2918614

  • 17Jul

    From the powershell command line run:

    Start-Process powershell -Verb runAs

    Hit “Yes” and you’re in!

    -Harry Caskey

    Tags: ,

  • 20Jun

    I ran into an issue where after deploying an image with SCCM 2012 R2 the client would not pickup the PKI certificate.  If you are not receiving packages from your server this could be why.  To resolve this you have to modify the “ProvisioningMode” registry key and clear the value in “SystemTaskExcludes” registry key.  To simply this and make sure this is working on all clients I would recommend pushing this registry setting out through group policy.



    ProvisioningMode = True

    SystemTaskExcludes = [null]



  • 07Mar

    I came across an instance where I needed to upgrade a Windows 7 image to Windows 8.1 and then capture that image for deployment with System Center Configuration Manager 2012 R2. I found out shortly after starting this task that when you upgrade an operating system you can no longer run SysPrep. So I started looking around and modifying registry keys and running commands.


    Below is the method that I found to work perfectly.

    Remove this KEY from the Registry:

    Remove this REG_DWORD from the Registry:

    Set this REG_DWORD from the Registry:
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\CleanupState [Set Hexadecimal Value: 7]

    Run this command as Administrator:
    slmgr /dli

    After your operating system is activated re-run SysPrep and it will work!

    – Harry Caskey

    Tags: , , , ,

« Previous Entries