First off: Thank you POCEH for your remarks on local user accounts and consequences of this on reaching other servers. --- I struggled with the same issue as OP and probably also mr Boltzman. I...
See more...
First off: Thank you POCEH for your remarks on local user accounts and consequences of this on reaching other servers. --- I struggled with the same issue as OP and probably also mr Boltzman. I did not get the exact same errormessages, but I had the same idea of virtualizing to a share on another server. This did not work and the converter-log was swamped with "Sysimgbase_Disklib_Getinfo failed with access denied", "FileIO-unlock", "Error 327689 opening disk", "FileIO lock ... lock timed out", "Locking of virtual disk failed..." etc I found a solution on this link: https://nikolar.com/2015/03/10/creating-network-share-with-anonymous-access/ This described what is needed to secure anonymous access to a share. In my case I have configured several places so I am not sure how much of my changes were actually needed, but the last configs was in Windows Local Security Policy with "Network access: Shares that can be accessed anonymously" incl my sharename and "Network access: Named pipes that can be accessed anonymously". I think the opening for anonymous tricked it. I made (at least) the following configs on the server with the sharename: - No UAC and win firewalls - Enable guestaccount - Add guest and anonymous with full access to the shared folder Local security policy (Security settings/Local policies/Security Options): - Accounts: Guest account status – change to Enabled - Network access: Let Everyone permissions apply to anonymous users – change to Enabled - Network access: Restrict anonymous access to Named Pipes and Shares – change to Disabled - Network access: Shares that can be accessed anonymously – enter name of share you created in the text field My setup: - Source: Virtual win2012R2 - Destination: Share on other virtual win2012R2 - Same subnet - Converter 6.2.7348398 I have a current case in a prod-environment were the above could be usefull but I doubt I can get away with all these changes in the security profile. For my prod-case I think I will go for running the P2V from another server in the same subnet which luckily has access to a vCenter.