mikkydoos

I discovered where I had gone wrong. I must have used a MAK key and not a GVLK key when I was creating my fat image.... this deployment isn't being done with a thin image and MDT. Sysprep doesn't strip out the license key as I assumed so when activating before I renewed it was activating online with the MAK key. When I renewed our licensing the MAK key was expired and couldn't activate. slmgr.exe and cscript are now my best friends - check your keys are all GVLK for the correct versions. For Office key management use cscript ... https://docs.microsoft.com/en-us/deployoffice/vlactivation/tools-to-manage-volume-activation-of-office Hadn't seen it before. Handy As soon as I used the GVLK key for Windows and Office they both activated perfectly from ADBA. Doh!

What sort of money were they talking @PR-UK ?

@timbo343 I appreciate you want to state something positive. I respect that. For everyone else thinking of or already using using this product... I've used this product since it was Junior Lbrarian locally hosted. This bunch of clowns have had years to sort it out and had plenty of time to get it right. Their support is uncontactable. I keep missing the cancellation until it gets into 90 days, which is an unheard of customer retainment strategy nowadays. They recently sent me a copy of T&C's I signed a decade ago, way before Capita had anything to do with them, to force their non-cancellation point. They're a bunch of crooks. I hope they go bump very soon, very hard.

Any more advice for storage spaces configuration guys. I'm looking at this too. Bit confused on the hardware requirements. Disks... cache and storage pools make sense but the rest of the hardware ? CPU? RAM? Separate OS array ? Switch ? EDIT: Just found this which is pretty informative... https://lenovopress.com/lp0064.pdf

Hi all, I have an issue whereby new installs fail to activate Windows 10 2016 LTSB after renewing our Microsoft licensing. I'm missing something here but not sure what ? Our MS licensing renewed last week. I've been activating with ADBA on a 2012 server which has been working fine activating Windows and Office 2016 with KMS keys upon domain join which occurs during setup. A couple of days ago I built a couple of machines from an image installed from WDS. They didn't AD activate.... Error = 0xc004c003 license key invalid. Office had activated but not Windows. I replaced the KMS keys on the ADBA server with the ones generated from the latest MS agreement and I've also added the MAK and CSLV keys in VAMT - both windows and Office for manual activations. I re-installed the image - No Windows activation. The client is showing it has a key. This is the MAK key that was used when the image was created. I'll call this the old key. The image is sysprepped (OOBE) which should scrub out the key completely right ?. Also this old MAK key was used in our unattended .xml - which I've since changed to a new key and re-installed my tests - but the client still won't activate and stills shows the old key and an error. To test I fired up a vanilla VM with no unattended.xml. This activated but not with one of my keys ?.. or is this a GVLK key that will expire? Day 2: _____ Another test of the same image in a VM this morning and it activates... but with the old key... note this key isn't added to ADBA, VAMT or in my unattended.xml, but it is the key that I used when creating the image. Same test on a physical machine....same image, same AD, same unattended.xml.... fails with error in the first picture! What ???? 1. Where the hell is that old key coming from ? 2. Why has Windows suddenly stopped activating after I renew our licensing - or is this a massive coincidence. 3. Where has that random key come from in the vanilla install ? 4. Why will a VM activate and a physical machine not? Mightily confused :mmph::mmph::mmph::mmph::mmph: Cheers in advance

No changes except the Mojave update. Both PCuts on the same version. IOS printing has been restarted. Like I said in the OP, the print gets from the Ipad to the Mac, is present in the windows PCut Mac queue and available to the MFD. It just doesn't pull the job through.

Yes. It has been working. Yep. All set fine

Hi all, I wonder if anyone has come across this... I've had this before and it has resurfaced (i think) after updating our Mac mini secondary Papercut server to Mojave. Printers on the Mac are online and correctly configured. I have re-run 'Control Printer Monitoring.control' on the Mac to 're-sync' to the primary Windows PaperCut server. Restarted the Papercut services on the primary server. Mac printers/queues appear OK in primary Papercut server and are configured correctly to release on the appropriate devices. Printers appear in the print dialogue on iPad and jobs are queued in the PaperCut app on iPad. Once printed the job appears in the app as pending release. On the MFD the job is listed under the users logon. .... when the print is released, nothing comes out and the job is lost. Any printing from Windows as the same user works fine. Can anyone suggest where else I can investigate? Cheers in advance

I'm fighting with MLS at the moment over our cancellation within their 90 day period. I demanded to see our signed T's & C's... they sent me the original contract I signed for in 2009. Is that legal for them to use a contract that is that old and will have been renewed 10 times without re-signing??

I did try with a new user but didn't delete the other one. I'll try that out.

No you can't but sysprep passes all the pre checks before erroring on this one so it seems that it will. I'm confused as LTSC doesn't (!!!) isn't supposed to have AppX but its failing on an AppX app. ?????????

Hi all, Has anyone experienced this with LTSC 1809 ? Sysplop is failing with what looks like a provisioned app issue. Get-AppXProvisionedPackage lists nothing.... literally... I presume because there aren't any provisioned apps in LTSC.... hence I can't remove it. The failure in the sysprep log is: Failed package 'Microsoft.Windows.SecondaryTileExperience' 'Failed to remove apps for the current user: 0x80073cf2' This is an in place upgrade from an 1607 LTSC image which did sysprep. Any suggestions appreciated. As usual.. hardly anything on the 'net. Cheers in advance

I use the same as @LeMarchand ....PRM. They're pretty good. Certificates accurate and free if over a minimum quantity of items..... and a free mug sometimes.

Here it is.... found it. Couldn't see for looking [ATTACH=CONFIG]51951[/ATTACH]

Thats where I am but no setting for display

This local setting keeps the screen alive... Very annoying that theres seemingly no group policy setting in 'Control Panel/System/Power Management' to deal with the screen timeouts. Windows 10 default is 20mins which is too short for me!

That setting only removes the Ctrl-Alt-Del screen. It locks again after 10 mins or the screen goes blank. What I want to happen is for the screen to stay alive and the desktop remain visible without intervention until the user logs out. There must be a timeout setting somewhere.... on with the search

Cheers @FishCustard I've been looking at that but doesn't it just remove the lock screen rather than prevent it from locking? Giving it a bash to test.

Hi all, I'm a bit stuck on finding the right group policy setting for Win10 (LTSC 1607 & 1809) to turn off the lock screen for machines connected to a projector/screen. My scenario with Windows 7 was this: a) User OU GP ---- Set a screen saver ---- for users logging onto any machine to force a lock screen after x minutes b) Computer OU (screens/whiteboards) ---- Disables the screensaver using loopback processing for specific machines Those settings are now depreciated so neither now work on W10... but I want to achieve the same thing. Is anyone doing this successfully? Cheers in advance

Its been doing that for a while.

Me too. Misco were quite good. Then they were terrible. then they went bust!

Look at Starwinds

Always been really good for me. Business and personal.

Nor me. But should you be using UE-V with 10 instead ? I havent fully rolled out so can't yet.

Oh indeed. You voluntarily opted to end your life. Are you still breathing ?