Activate Windows Thin Pc
Alexander Rodriguez
2663820 FIX: You cannot activate Windows Embedded POSReady 7 by using a Multiple Activation Key if Internet access is not available For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
This time the replacement comes (after waiting 4 weeks - no stock in New Zealand and maybe Australia?), I boot it up and find Windows is not activated. Plug in ethernet, does not activate automatically.
This stemmed from a faulty (dead HDD) in the Thin Client. Are you saying I need to contact Microsoft to deactivate its OEM BIOS Windows license key before getting a replacement under warranty from HP?
no i think HP needs to contact microsoft to see if my guess about the number of activations is correct at this point you seem to be in the middle MS will direct you to HP, and HP has no idea what to do
I can see what you're saying but HP would surely have several or dozens of these thin clients activating every day, I don't think me getting 5 replacement units over a month period would affect the MS activation too much.
again, the ms activation servers use checks to try to stop illeagal activations and several of those are the number of activations made from the same hardware id's and also the frequency of activation attempts made within a set time frame
several years ago we had a unstable white box win 7 using a legit oem key that after 8 OS reloads/activations within 48 hours refused to activate anymore calling MS we were told that due to the number of activations that key was blocked
HP sent me a 768251-001 to test as a replacement - this activates fine BUT I have found there is a difference I didn't realise - this one doesn't have a Wi-Fi card. Otherwise the models are identical.
The client may fail to activate, when upgrading a Dell Wyse Thin Client from Windows 10 IoT Enterprise LTSB 2016 to Windows 10 IoT Enterprise 2019 LTSC. Nonactivated Windows can continue to function in deferred mode.
I've got some HP T620's and they have got Windows 7 embedded installed standard. I'm using HP Device Manager for new images and when I install Windows 10 IoT on the thin client, I can't activate Windows 10 IoT on them.
The error: "We can't activate Windows on this device because the product key was already user on another device. If you think it wasn't user on another device, select Troubleshoot below. Error code: 0xC004C008."
On another circumstance the Windows Key was showing a wrong key in the Windows Activation dialog but when using wmic it provided the correct one that could be entered and then it activated correctly:
I got a Dell Wyse 5070 Extended Thin Client which came with Windows 10 IoT Enterprise LTSC 2019 which worked until now. But because we require more local storage we replaced the 32GB SSD with a larger one (Micron 5100 1TB). After replacement I went to the Dell website, downloaded the latest Windows 10 IoT Enterprise LTSC 2019 image for my thin client, created a bootable USB stick with the Dell USB tool, booted the thin client from it and installed Windows.
We can't activate Windows on this device because you don't have a valid digital license or product key. If you do think you have a valid license or product key, select Troubleshoot below. Error code: 0xc004c003
All to no avail. Lastly, I tried the phone activation again but managed to get connected with a human agent. After obtaining the necessary information for him he told me that the product key was blocked by Microsoft and gone "back to the manufacturer" (Dell) and that there is nothing he or Microsoft could do.
I understand that this is just a single device (in my case, a web search suggests that this isn't exactly uncommon, it appears MS blocked a whole range of keys for no reason) but thinking of it, shenanigans like this and the inability of Microsoft to fix a problem they created in the first place makes them a huge liability.
Windows licencing can be a pain. I see that Windows want to drop that version of their OS and maybe that has something to do with it. Also, I seem to remember from somewhere that manufactures could get cheaper Windows licences if they kept the SSD storage below 64 GB (or maybe it was 32 GB) and so your attempt to put in a larger capacity SSD may have tripped that criteria. In any event, you are stuck between two non moveable organisations and neither want to be helpful.
Windows licencing can be a pain. I see that Windows want to drop that version of their OS and maybe that has something to do with it. Also, I seem to remember from somewhere that manufactures could get cheaper Windows licences if they kept the SSD storage below 64 GB (or maybe it was 32 GB) and so your attempt to put in a larger capacity SSD may have tripped that criteria.
While I'm not up on the current state of thin clients, I've never heard of anything shipped from a manufacturer with Win Enterprise installed unless you have a special deal where they preinstall your custom built image for you. Enterprise licensing is done between you and Microsoft via volume licensing. Dell sells VL licenses but you access your keys directly from Microsoft via the VLSC. I can't imaging a thin client coming with an Enterprise key embedded in the BIOS.
True (and I have amended my original post to reflect that it's IoT) but that doesn't change anything regarding the original problem, which is that Microsoft for some reason has blocked a completely genuine product key while pointing fingers to Dell for resolution, leaving me hanging in the middle.
Install macrium reflect on the wyse and create a bootable flash drive. Buy a m.2 sata drive enclosure. Install the old drive in the enclosure. Goto the setup and turn on usb boot, and turn off secure boot. Restart the wyse and press F12 at dell logo and boot it with usb. Connect the old drive and clone it to the new drive. Make sure C: partition is the last partition on the new drive so you can expand it later using disk management in windows. You can turn on secure boot and turn off usb boot in the setup.
Press F12 at boot and boot from usb and go to Troubleshoot and Command Prompt. Type diskpart enter. Type list disk enter. Type select disk x enter using the number from list disk. Type clean enter. Restart the unit and press F12. Boot from usb and install windows 10. Install the downloaded drivers and activate windows.
When a snapshot is created, the system image is generalized and the activation is canceled. On installing a snapshot, the system is activated by connecting to a Microsoft online service if Internet access is available. However, running the thin client in an environment without Internet access is also possible.
If the thin client is never connected to the Internet, it remains in the state "deferred activation", and the thin client can be operated without any restrictions. If activation fails, the thin client goes into the state "not activated"; in this case, a watermark may be displayed.
Hopefully this maybe helps somebody as it helped me. I wasnt able to figure out how the restrictions are set. My bet were local policies or registry changes but I didnt know there are direct options for this in the Administrative tools. With this knowledge everything became possible.
Another Thin PC feature that can help beleaguered system administrators manage their systems is the Enhanced Write Filter (EWF), a technology that can prevent permanent changes from being made to the OS by the end user. Windows Thin PC can, using a RAMdisk and unpartitioned space on the hard disk, store any write operations that the user makes to the drive. So, in essence, if you save a file to the desktop or install a program, it will be written to the EWF volume instead of the main Windows partition. Since records of these extra files are not stored on the main system partition, the user is presented with a clean OS upon rebooting. This keeps the machines easy-to-fix in the event of spyware or virus infection, with the added benefit of discouraging client-end computing and encouraging users to connect to the remote server to get anything done.
We are having this issue with the last few versions of IGEL firmware, we never had it until then but it started occurring for us within the last few months. We're attempting to get IGEL to look into the issue but they are pointing fingers back at Citrix.
Is there a reason why displaying X errors is the default behavior of Linux Workspace, and why we have to disable each error individually? This is a poor user and administrator experience and it makes much more sense to have this as an opt-in rather than opt-out setting, since this information would not be useful to the vast majority of users/admins unless they were specifically looking for debug info. I also don't want to have to figure out every single X error that a user might experience to include it in this setting, not to mention that it seems to be very difficult to find a comprehensive list of X.Org error codes.
This knowledge base created by MiniTool introduces a kind of lightweight operating system (OS) called Windows Thin PC, which is based on Windows 7 and designed for thin clients. To learn more information about WinTPC, just read the below content!
Windows Thin PC (WinTPC), released in 2011, is a Microsoft Software Assurance (SA) benefit that offers a low footprint, locked down version of Windows 7. It allows organizations to reuse existing PCs as thin clients to reduce the need for new thin client machine.
dd2b598166