windows 2019
7 TopicsWindows Admin Center Performance stats for cluster
I have a 3 Node Server 2019 cluster running S2D and up until recently all the performance stats worked. Last week the stats for the disk and network stopped working and I can't get them back. I've rebooted the servers, rebooted the computer WAC is on and updated it to the latest and still no luck. Any advice? Thanks868Views0likes4CommentsVeeam B&R backup jobs failed to login to Qnap Nas after KB5011503 installed
Good Morning, Veeam backup & Replication CE 11 (last release) installed on Windows Server 2019 Hyper-V VM from about 1 month Veeam Backup jobs use as destination a shared folder on Qnap Nas. Windows 2019 VM Italian language standalone, Qnap Nas under domain. R&W user used for Qnap autentication it's local user for Qnap and Administrator for Win2019 VM. All go fine before KB5011503 update After this installation Veeam Backup job works only with guest user. No other user can autenticate to Qnap with SMB 1, 2, 3 Error message on Qnap is "Processing MACHINENAME Error: Nome utente o password non corretta --tr:Error code: 0x0000052e Failed to process [isFileExists]. --tr:Client failed to process the command. Command: [isFileExists]. --tr:event:3:" Trying to uninstalKB5011503 update, after reboot all veeam Backup Job returns to work. UpdatingKB5011503 again all Job stop to work. Could be this a bug? Where I can report this to microsoft? Thanks Paolo22KViews0likes7CommentsQuestion about product key after windows inplace upgrade
Good morning, I have a windows server 2012R2 Standard license: WINDOWS SERVER 2012R2STDROK2CPU / 2VM LENOVO with related product key System is ok and active, all goes fine. I am now attempting to do an inplace upgrade to Windows 2019 server Standard, as the license should also be valid for this product. The inplace upgrade process goes fine but at the end Windows 2019 server is not activated. If I try to activate it, the PRODUCT KEY (of WIN SRV2012R2) is considered invalid: I also tried with this command: DISM /online /Set-Edition:ServerStandard /ProduckKey:XXXXXXXXX /AcceptEula but I catch an error: ERROR: 87 (invalid product key). What I'm missing? Is not possibile to do an inplace upgrade from 2012R2 to 2019 with ROK license? Thank you...4.1KViews0likes1CommentIs 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.2.2KViews0likes3CommentsNon Administrator user - stop windows service remotely
Hello, i upgrade my server form windows 2012 R2 to windows 2019 and now i cant stop and start service manually. i gave full permission to the user on the service but i still get this msg: [SC] OpenService FAILED 5: Access is denied. when i run this from remote computer, before the upgrade in 2012 all work fine thank a lot, RoeeSolved8KViews0likes2CommentsServer 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.3.5KViews0likes0Comments