Gatt

Thread: Resurrection (see what I did there?) Playing this on Steam for a while and tonight, on the XBox I finally made it past Seegson Comms - God that is a tense level and took a good few attempts (one attempt saw me make a good amount of progress and nearly completed the level only to be got by the Alien exiting a vent! Heart is still going ten to the dozen

I've got issues with Win10 not getting updates from Microsoft when connected to a WSUS I get the WSUS updates absolutely fine, but if I click "Check online for updates" I get an error code (Don't have it to hand) I have to delete the Registry key for the WU policy and then I can get online updates (including insider preview builds)

Possibly: Shortly followed with: And ultimately:

Wrong show

Great news! But yeah I was getting vibes that this could be US only - which would suck big time considering Trek has fans world(s) wide!

A bigger threat would be that carpet!

We've all been here..

I agree, given how quickly software (OSes and Apps, etc) change, then it makes sense to have your deployment platform as up to date as possible!

...long live ConfigMgr as a Service.. Microsoft System Center Configuration Manager next up to get the service treatment | ZDNet

...how about these as well? Fore!: Amazon.co.uk: Music

I'm struggling to get this working with MST 2013 Update 1 Ive configured ZTIGather.xml and the MDT Database and added the necessary changes to allow for OSDAdpater1 All goes well, I can enter the necessary configuration in the console But, when I boot and start to run the TS, it bombs out with: FAILURE (7813) : False : Verify there are partitions defined in this task sequence step Looking at BDD.log I see this for the 2nd NIC: Property OSDDISKINDEX is now = Test LAN Obtained OSDDISKINDEX value from SQL: OSDDISKINDEX = Test LAN Property OSDPARTITIONS is now = 00:0C:29:A9:B0:92 Obtained OSDPARTITIONS value from SQL: OSDPARTITIONS = 00:0C:29:A9:B0:92 Property OSDPARTITIONS0TYPE is now = FALSE Obtained OSDPARTITIONS0TYPE value from SQL: OSDPARTITIONS0TYPE = FALSE Property OSDPARTITIONS0FILESYSTEM is now = 10.0.0.5 Obtained OSDPARTITIONS0FILESYSTEM value from SQL: OSDPARTITIONS0FILESYSTEM = 10.0.0.5 Property OSDPARTITIONS0BOOTABLE is now = 255.255.255.0 Obtained OSDPARTITIONS0BOOTABLE value from SQL: OSDPARTITIONS0BOOTABLE = 255.255.255.0 This clearly isn't right and should be being set as OSDAdapter1...

Reminds me of creating sprites on the ZX Spectrum and C64!

Does this work with pre-windows 10 OS's? Do applications work from Software Center on an existing client? Have you got your boundaries in a Boundary Group? Are the applications fully deployed to a distribution point? Have you allowed your applications to be installed as part of a task sequence? (Check the General Information tab on you Application for a tick box in the middle)

The room had been trialed with Thin Clients and we were having issues with the Wyse terminals dropping off the network I'd been trying suss out what was actually wrong, had gone on leave (Easter I think..) and when I came back - The RDS Server was now upon the cabinet.. They {who shall remain nameless to protect the guilty} thought that it would be quicker if it was in the same room.. Needless to say I wasn't overly impressed, and it didn't make a blind bit of difference!

I think it is possible - you'll need a Win10 Boot and Install WIM (obviously..)