Re: Windows Server 2012 Build 9200 Activator
Stephanie Dejoode
Hello all, we also have exactly the same problem here and can also confirm the workaround with the uninstallation of the two KBs. We do not want to open another case. Have you received an answer from MS in the meantime or have you made any progress?
We are still running a hyper-v cluster with windows server 2012 Datacenter (OEM). These soon to be unsupported systems will be migrated to our new HCI infrastructure with Windows Server 2022 by the end of October.
We suspect that the problem is that our WSUS server first distributed the two KBs that we installed. Subsequently, the SSU (KB5030330) was distributed and also installed. However, MS recommends installing the SSU first.
Hi, Our company need to reformat our 2 servers with hyper V, done with the 1st server, how can we registered or activate it again using our previous license key? I have the screenshot of computer properties it needed.
Since you're using volume license product keys you should have also used volume center download so the channels line up. As a work around you can try using kms keys as intermediate step.
-us/windows-server/get-started/kmsclientkeys#windows-server-2012-r2
hi @JoyDutt , thanks for the reply, i though it can be activated buy simply re-entering the previous license key which was a VLS product, and now expired, so in my case, does it means i need to purchase a new license again to have it activate?
I can log back in with Remote Desktop, get the same error, but am back exactly where I left off before being disconnected. It's as if I disconnect the session without logging out, leaving the session still running.
I'm new with multipoint server and I'm trying to allow my users connected via direct video-connected station, to safely remove usb flash drives. I modified the values in the Local group policy to allow Administrators and Interactive Users to eject and format removable media. However the user is always prompted to type in Admin password in order to safely eject.
Getting error message "Shell has stopped working" on virtual machines.
Due to this error, no more able to use system, no any option accessible, it stuck until i reboot the virtual machine.
This is happening randomly.The OS is Windows Multipoint Server 2012.
I'm currently experiencing a problem with our server. I can't open my multipoint dashboard. whenever i'll click the icon there's a pop op dialog box that says "wms dashboard has stopped working". I've tried some resolve on the net for the 2016 but it doesn't fix the problem. All clients connected to this server shows "station blocked" and cannot be accessed.. Please help. Thank you.
I have two monitors connected to my video card. A mouse/keyboard connected to my front IO, and another set connected directly to my motherboard. Instructions specify to use usb hubs for each station, before I go buy some I just wanted to make sure I was able to add a station.
2. In Multipoint Dashboard I can Block station only ONCE (first time) after its login. Then I can unblock station normally and second block already doesn't work. After logout station and login back, I can surprisingly block station again for the first time but again only once. (Don't know if there could be something with memory...)
i am evaluation windows server 2016 multipoint point service. it's not in an educational senario. I just want to share the PC with my wife or my kid, so two concurrent users is OK. My installation is given a remote desktop grace period of 120 days. I wonder whether its possible to work with remote desktop restricted admin mode? -desktop-services-enable-restricted-admin-mode.aspx
I can try the restricted admin mode configuration, but i have to make sure that it won't cause my windows server 2016 failed to start with multipoint service enabled. I have a PCIE video card and an mainboard integrated video card. Making change of the boot video card in BIOS will cause multipoint server 2016 fail to start. But i can simply revert the BIOS setting to fix this. If i make changes to the remote desktop service and multipoint server 2016 fail to start, what shall i do to rescue?
In task manager -> user tab, if i logoff the user WmsShell, I can return to an environment like normal windows without multipoint service. But can i re-enter the multipoint service with some command instead of restarting? Is it possible to configure windows 2016 to start just normal, and enter Multipoint environment after running some command?
Hi there.
I'm Pretty new to the Server systems so I'm still getting the hang of it. But I'm having a problem with the MultiPoint Manager, On all the Work stations (WS) and desktop (DSK) they can connect to each other easily with no problems but the server cant connect to the WS and DSK It keeps coming up saying The specified server name is not a valid hostname, not a valid address, is not reachable, or points to the local server. Please Verify whether the server is reachable But I'm putting in all the right Security information and passwords and usernames the same I used to put into the WS and DSK what connected to each other. If possible could I get someone to help me please as im new to all the server stuff
Using Windows MultiPoint Server 2012, and successfully managed to create a virtual desktop. Now when I try to start it up, I get a message saying "Waiting for [virtual desktop name] to start", and it just hangs with the timer still running, no matter how long. Then when I go to the "Home" tab, I can see the virtual desktop in question, with a yellow triangle next to it.
We have a Physical Server running the Window Server Multipoint 2012 Premium Edition OS and now want to move the Physical box as a VM to a Hyper-V Host. using the Disk2VHD tool. Currently the server is addtionally running the Hyper-V role but there are no VM's running on this Host. Can i uninstall the Hyper-V Role from the Multipoint server will this affect any functions related to Multipoint ?
The log below would indicate to me that it's requesting an IP and just not getting an answer, but I know the DHCP doesn't have issues as every other device, and even the wifi interface on the same machine get an IP without issue.
However just from the outputs we have so far it seems that both NM and dhcpcd are in agreement over the issue when trying to manage the interface. Which moves the likely culprit to the entity they have in common, which is the kernel and more specifically the kernel module that should be giving you access to this network interface.
So check your dmesg/journalctl -k on whether any errors are logged with regards to the module that's supposed to give you the network interface, maybe even try to downgrade the kernel to a known working version or so.
I don't really see any useful information here that could help me get to the root of the issue. It looks like it retries and just cannot get a response from the dhcp server, but what I don't understand is how this could be an issue with 2 separate routers that also incidentally work with every other device and interface, and indeed this very same interface under Windows (and I assume it would work under a livecd as well).
I'm sorry for not posting this sooner, but the issue here is likely related to the dual-boot configuration I was using at the time. It appears that windows authorizes itself to modify device firmware outside of its own scope, which made the device incompatible with the Linux driver.
b1e95dc632