User Profile
IT_Nick
Brass Contributor
Joined 4 years ago
User Widgets
Recent Discussions
Re: Remote assistance with Quick Assist is changing
"LITERALLY TWENTY-ONE Minutes to make a Quick-Assist connection." your comments are 100 percent accurate, the dangerous default web search is lethal for the older generation and the less IT literate (but hey ho web results first mean they can slide in some paid adverts. The fact it might take them to a dodgy lookalike trojan with a backdoor in it is not their problem right?) Equally your comment about the hidden "sign out" and "switch user" is also very relevant. Took me a minute or two to realise that my remote user on the phone wasn't blind and the option to sign out was genuinely not on screen. We have a domain and keep trying to tie it down security wise because you know, ransomware is a thing and current cyberwarfare threat levels are just a tad high. QED users are not allowed to install anything and almost everything requires elevation. Guess what, GPO deployment of QuickAssist via Power Shell script fails because it runs in the user context. Microsoft has a workaround though, pay them thousands of dollars extra per year for a licence tier that includes Intune of course. I begin to suspect this is not accidental but a long standing pattern. MicroShaft tests new features on the users for free (unpaid beta testing), and once it refines them (release candidate) it removes them from the "free" level to put them behind a paywall of a higher licence tier. You might be forgiven for suspecting the lack of an MSI is a deliberate "feature" of the new QA experience. 😞333Views2likes0CommentsRe: HOW-TO : Use VAMT 3.1 for Windows Server activation 2016 through 2022 and license management
Karl-WE Hi Karl, Noticed something weird in VAMT under AD Based Activation. My CSVLK Volume_KMS_WS22 channel key is only showing supported products of Windows 8 and Server 2012. However in Product Keys the Same CSVLK is showing as Edition: ServerDatacentre;ServerStandard with a Description Windows Server 2021 RTM ServerDatacenter;ServerStandard. Is this yet another bug or do I have the wrong CSVLK for 2022? Thanks Nick3.6KViews0likes0CommentsRe: HOW-TO : Use VAMT 3.1 for Windows Server activation 2016 through 2022 and license management
Karl-WE Hi Karl, Thanks for the workaround but I am not sure it will fix my problem. I am having the same problem when adding 2022 MAK keys to VAMT 3.1. I am migrating an ancient 2012 R2 server VAMT over to a new 2022 server. I followed the MS documentation and installed the server, installed SQL Express 2022, then the latest ADK. Connected the VAMT to the SQL creating a new table for it. I brought in the backup I did of keys etc from the old server and imported them without a problem. I then added my new CSVLK for 2022 also without a problem. However, when I tried to bring in the MAK keys for 2022 I got the same error as you show in the article which this workaround is linked to. Any ideas on what is going on here and if there is a workaround for this? Any assistance greatly appreciated. Thanks Nick3.8KViews1like2CommentsRe: RDS and HP Thin Clients
Sorry I couldn't help, I am finding this a difficult subject to get answers on. Linux and Microsoft Licencing are two uncomfortable bedfellows as the Open Source nature of Linux means that MS is rather reluctant to publish details of how its licencing works with it I fear.2.7KViews0likes0CommentsRe: RDS and HP Thin Clients
device CALs cannot be reassigned I believe so your W7 ThinClients may have consumed the licence already. My thinking is if the Hardware ID of the Device is some sort of hash of the clients MAC address (quick and dirty way of ID'ing a remote machine) then it may still be identifying the old W7 ThinClients as activated and looking for the Windows 7 Registry Keys to validate them. It wont find them so it drops the session after a default period possibly the 60 minutes you have identified. have a look at this and see if it helps https://techcommunity.microsoft.com/t5/ask-the-performance-team/multiple-per-device-rds-cals-are-issued-the-same-device-issue/ba-p/3756392.9KViews0likes2CommentsRe: RDS and HP Thin Clients
Hi I have a similar question about RDS Device CALs and Linux OS Thin Clients. Question is how does it work with a Linux device like the HP ThinPro. Mike D also asked how the per device CAL is stored for the same reason 2 years ago. https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/rds-device-cals-with-thin-clients/td-p/774068 There doesn't seem to be much help on this subject.2.9KViews0likes4Comments
Recent Blog Articles
No content to show