Sašo's questions

I have a Hyper-V server, also running Windows Admin Center, let's call it FISH. That server is set up as gateway. On it, there are two storage pools, which can be managed via the Server Manager normally, and some VMs.

In Windows Admin Center, Storage Spaces (Direct) is not available in server management, and from what I gathered, I need to connect to a Cluster.

I have tried to add a cluster, but I am having issues. Using FISH.local appears to find the server/cluster, however using usernames Administrator, FISH\Administrator or FISH.local\Administrator yields the following error:

Access was denied to "FISH.local". You can still add it to your connections list, but you'll need to provide administrator credentials to connect to the cluster.

In WAC settings it says I am signed in as "FISH\Administrator", so I am a bit at a loss. Does cluster management require a different kind of Administrator account/permissions?

While doing VM testing, I have, out of curiosity, ticked Enable nested virtualization in the Processor tab in Windows Admin Center (Version 2103.2 Build 1.3.2105.24004).

Trying to start the VM returns this error, which makes sense:

RemoteException: Failed to start virtual machine VM NAME. Error: 'VM NAME' failed to start. 'VM NAME' could not initialize. The virtual machine could not be started because this platform does not support nested virtualization. 'VM NAME' failed to start. (Virtual machine ID ) 'VM NAME' failed to start worker process: Unspecified error (0x80004005). (Virtual machine ID ) 'VM NAME' could not initialize. (Virtual machine ID ) The virtual machine could not be started because this platform does not support nested virtualization. Consider not exposing virtualization extensions to the virtual machine.

However, after this change, I am unable to untick Enable nested virtualization, as saving immediately ticks it again. How do I disable it so the VM can run again?

While printing to a network shared printer, some documents printed from Windows XP machines cause an additional page to be printed with the following text

PCL XL error

       Warning: IllegalMediaSource

However, when printing on Windows 7 machines, there is no such issue. What causes this and how to fix it?

Related: Scheduled Robocopy task fails with 0x10 error

I'm using robocopy as part of a server backup script. It fetches the files to this workstation (Windows 7, upgraded from Vista - that caused some quirks before), and then copies them to a server in LAN (Windows Server 2000).

robocopy H:\folder \\SERVER\drive\folder /MIR /LOG:H:\backup.log /TBD /TEE

When this task runs in scheduled tasks, usually the network folder has not been accessed yet by the computer since startup. As such, it usually ends up failing:

-------------------------------------------------------------------------------
   ROBOCOPY     ::     Robust File Copy for Windows                              
-------------------------------------------------------------------------------

  Started : Fri Jul 12 16:16:03 2013

2013/07/12 16:16:03 ERROR 3 (0x00000003) Getting File System Type of Destination \\SERVER\drive\folder
The system cannot find the path specified.


   Source : H:\folder
     Dest - \\SERVER\drive\folder

    Files : *.*

  Options : *.* /TBD /TEE /S /E /COPY:DAT /PURGE /MIR /R:1000000 /W:30 

------------------------------------------------------------------------------

2013/07/12 16:16:03 ERROR 3 (0x00000003) Creating Destination Directory \\SERVER\drive\folder
The system cannot find the path specified.

As you can see, I tried using /TBD switch to wait for network share names to be defined. It did not help. However, forcing the scheduled task to run manually later successfully updates all the files. Though I didn't access the server backup folder during that time, I did access a different share on the server.

What should I do? Add a retry in the batch script? Or use a different program to make sure the network path is available before continuing?

Background: I'm working on a hole punching service with UDP, and in order to differentiate users under the same public IP, I've thought of making the user also send their local IP. That way, I killed 2 birds with 1 stone: Clients are uniquely identified, while also making the server offer users to establish a direct connection (if possible), rather than hairpinning it.

All seemed perfect (especially the unique identification), until I realized this is possible:

So here's the actual question: How widespread are such situations, if they are even used, and where?