Home

Hello,

A very common error is the famous "CredSSP encryption oracle remediation" message error due to may 2018 update when it's installed on the server but not on the desktop (or the opposite).

Hello,

Can some one help me out from below scenario.

Current Operating System-Windows 2012r2

Roles enabled in server are-WSUS,RDWEB,IIS

Planning Operating System-Windows 2016 DC

Machine hosted in vmware

Upgrade status-Rolling back to previous version i.e Windows 2012r2

Error after upgrade screen-the installation failed in the safe_os phase with an error during migrate_data operation

Issue Description-I can see Windows 2016 Installation complete status and after restart getting above error and rolling back to previous version.

Things I did before upgrade-

Cleaned WSUS roles and dependencies

Make sure enough space on C Drive

I had done many os upgrades with above featured servers but this is the first scenario ever seen

Points Noted-I can see one user profile disk in current server,does it would be the blocker if it is the blocker please help me out how to get rid off this from else suggest with other solutions to overcome this issue.

Thanks in Advance,

Raj

can you also post your playbook?

Must have been telepathy 😉

able to ping the machine, but playbook fails at win_update module....

TASK [update packages with excluded list] ***************************************************************************************************************************************************************************************************
task path: /home/svc-gfilinux/test-win-playbook.yml:5
 [WARNING]: ansible_winrm_tranport unsupported by pywinrm (is an up-to-date version of pywinrm installed?)

Using module file /usr/lib/python2.7/site-packages/ansible/modules/windows/win_updates.ps1
<lax-lod-clt12c.csodsandbox.corp> ESTABLISH WINRM CONNECTION FOR USER: svc-gfilanguard@csodmgmt.corp on PORT 5985 TO lax-lod-clt12c.csodsandbox.corp
<lax-lod-clt12c.csodsandbox.corp> WINRM CONNECT: transport=ntlm endpoint=http://lax-lod-clt12c.csodsandbox.corp:5985/wsman
<lax-lod-clt12c.csodsandbox.corp> WINRM OPEN SHELL: 4A3946EB-6161-469C-B4C6-09222C7B89E2
EXEC (via pipeline wrapper)
<lax-lod-clt12c.csodsandbox.corp> WINRM EXEC 'PowerShell' ['-NoProfile', '-NonInteractive', '-ExecutionPolicy', 'Unrestricted', '-']
<lax-lod-clt12c.csodsandbox.corp> WINRM RESULT u'<Response code 1, out "", err "An error occurred wh">'
<lax-lod-clt12c.csodsandbox.corp> WINRM CLOSE SHELL: 4A3946EB-6161-469C-B4C6-09222C7B89E2
fatal: [lax-lod-clt12c.csodsandbox.corp]: FAILED! => {
    "changed": false,
    "module_stderr": "An error occurred while creating the pipeline.rn    + CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordE rn   xceptionrn    + FullyQualifiedErrorId : RuntimeExceptionrn rnValue does not fall within the expected range.rnAt line:280 char:26rn+ ... g_tasks = @($schedserv.GetRunningTasks(0) | Where-Object { $_.Name -e ...rn+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~rn    + CategoryInfo          : OperationStopped: (:) [], ArgumentExceptionrn    + FullyQualifiedErrorId : System.ArgumentExceptionrn rnrn",
    "module_stdout": "",
    "msg": "MODULE FAILURE",
    "rc": 1
}
        to retry, use: --limit @/home/svc-gfilinux/test-win-playbook.retry

PLAY RECAP **********************************************************************************************************************************************************************************************************************************
lax-lod-clt12c.csodsandbox.corp : ok=1    changed=0    unreachable=0    failed=1

Thank you for explain infinity rulls

it is Very complete

Wolfgang I don't know how you read my mind but I was just looking this information up this morning! Thank you!!