Jump to content


keety

Established Members
  • Content Count

    13
  • Joined

  • Last visited

  • Days Won

    1

keety last won the day on October 3 2014

keety had the most liked content!

Community Reputation

1 Neutral

1 Follower

About keety

  • Rank
    Member

Recent Profile Visitors

884 profile views
  1. How do, I don't suppose anyone knows of a way to suppress the firewall and Av warning messages that pop up in the action center? I know you could do it in Windows 7 and there were registry entries that would do the trick but these don;t work any more... I've been looking for a GPO but there doesn't seem to be one...
  2. Hello, Right, I've had the same issue and I've managed to fix it (well pinpoint where the issue is) It's affecting my Windows 8 and Windows 10 builds. It started happening a good 5 months or so ago, but seeing as I'm the only one testing and building these machines I looked into it for a bit, got fed up and moved on (it was only Windows 8 at the time, and I build those using media as its surface pro's) Anyway, I've been through everything, was it the WIM? Was it the fact I was pumping in an xml file to customise it? Was it drivers? After going through all of that I was no close
  3. Cool! Getting the same thing here as well... I'm guessing they didn't give you a rough estimate as to when it would be fixed though I hope we won't have to go through this every single time there's a point release... WaaS seems a bit more fiddly than I was expecting!
  4. HELP! Right, I've taken delivery of a nice new Surface Pro 4.. It's come with pro on it and i'm trying to upgrade it to Enterprise. I've managed to get Enterprise on by butting the latest iso onto usb and runnign that from the mahcine, but I've go tall sorts of issues with it (start menu not working etc) and none of the fixes work so I'm going to wipe and try again. I can't for the life of me get the thing to boot off of USB. Has anyone managed to get USB boot working on the Pro 4? I've tried the USB media for Windows 10 as well as SCCm 2012 boot media (with my Windows 10
  5. Managed to figure it out, had a hidden collection pushing and old version of the client out.... unsurprisingly it doesn't like trying to reinstall over the top of a newer version...
  6. Morning, got a weird issue here, current setup SCCM 2012 R2 CU3... We're seeing the config manager client re-install itself after OSD Completes successfully. It's not straight away, it can take 40 mins or so after OSD completes. We've noticed it because Software Centre goes walkabout... I'm installing the CU3 patch as part of OSD via the patch switch and that works. You can logon to the machine after OSD has completed and everything looks fine, software will install, patches will install, everythings great (no errors in logs for instance). Initially I thought it might be th
  7. Hi guys, not sure if this is the right place, but thought I'd post this up as I've spent a week trying to figure out how to get the Windows store working properly in our environment. Our environment is highly locked down because of the nature of what we do. Because of this the Windows store has been disabled. We've started trialling various Windows 8.1 devices for use as mobility solutions and it quickly became apparent that without the ModernUI apps the devices were basically very expensive laptops. Our users were after devices that had the freedom of an Ipad crossed with the functionali
  8. Right, fixed this myself. I had deployed the Task sequence so that only Boot Media and PXE (hidden) had access to this. To use a hidden TS you need to have a task sequence variable enabled called SMSTSPreferredAdvertID Set the variable to the Deployment ID of the Deployment of the specific Task Sequence that has been deployed to the Unknown Computers collection. Make sure you select the right deployment, I spent 15 mins trying to work out why it wasn't working, as I had had copied the deployment for the specific TS that wasn't advertised to the Unknown Computers collection.
  9. Probably network drivers. Make sure you've enabled debugging and press F8 went it boots up, make sure you;re getting an ip address. Although with it being hyper-v i'd imagine they drivers are inbox drivers and should be part of winPE. I've not played with hyper V much but I know on vmware you can set to a default legacy NIC. You can try re running teh task sequence by goign to x:\sms\bin\i38\tsbootshell.exe (for x86 use x64 for obviously x64) With new models of kit I've found it a bit fiddly getting the right drivers, I tend to use drvrload to load them up and make sure they work
  10. I had lots of weird oddities, until I put a restart in after installing Config Manager, I set that to boot into the OS and not back into WinPE and everything has been rock solid (10k deployments) since then.
  11. Have you tried re-starting WDS? Might have thrown a wobbler...
  12. Afternoon, I'm looking to deploy a TS via bootmedia to bare metal machines. I've already deployed lots of different TS's to all sorts of kit, so i'm fine and happy with that. However I know have a requirement to build bare metal tin. Ideally I'm going to get the chaps doing it via boot media. So far I have; Deployed the Task Sequence to Unknown Computers (Bootmedia and PXE (hidden) Built bootmedia with Unknown Computer support enabled (as well as the old OSD ComputerName variable) When I boot the media, I put the password in but it tells me there are no task sequence avail
×
×
  • Create New...