Is the spooler service supposed to work in new windows-insider image?
One of the things I tried is if the spooler service can be started and used in the new windows-insider image. PS C:\windows\system32> net start spooler net start spooler System error 1058 has occurred. The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. PS C:\> start-service spooler start-service spooler start-service : Service 'Print Spooler (spooler)' cannot be started due to the following error: Cannot start service spooler on computer '.'. At line:1 char:1 + start-service spooler + ~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service], ServiceCommandException + FullyQualifiedErrorId : CouldNotStartService,Microsoft.PowerShell.Commands.StartServiceCommand The services that the spooler service depends on seem to work, so I wonder what may be missing. The first use-case for us would be a elegant test environment for our client software packaged as MSI. At the moment I have to spin up a VM and run unattend MSI installation and running some tests. Using a Windows container would speed up our pipeline a lot as we always can have a clean Windows environment in seconds.
Server 2019 %username%
Running Server 2019 I've noticed that the %username% variable is now set to SYSTEM. With Server 2016, when a user runs a batch file I can use the %username% variable to return the name of the user running the session. However, with Server 2019, when a user runs a batch, the %username% variable returns as SYSTEM. I'm getting around this by parsing %userprofile% to find the name. Should we expect this to be a change in how Server 2019 operates? I should note that I am running build 17723.
