Jump to content


lord_hydrax

Established Members
  • Posts

    122
  • Joined

  • Last visited

  • Days Won

    2

lord_hydrax last won the day on January 21 2020

lord_hydrax had the most liked content!

About lord_hydrax

  • Birthday 05/26/1985

Profile Information

  • Gender
    Male
  • Location
    Melbourne, Australia

lord_hydrax's Achievements

Newbie

Newbie (1/14)

2

Reputation

1

Community Answers

  1. googling around people seemed to have problems with permissions on the above folder so I just reapplied the permissions and reinstalled and it worked...
  2. I checked permissions on D:\Program Files\Microsoft Configuration Manager\OSD\bin and both System and local admins have full control
  3. Hi, We are having trouble pxe booting devices, got another thread about that. I read we should probably update our SCCM version somewhere so I thought I would give that a crack. Pre-req checks seemed good. Ran the update and its failed. The console says the version updated but I think half the install didn't work. Attached is the log can someone please assist? CMUpdate.log
  4. Hi, I'm having trouble with the surface dock. I added the Surface dock ethernet driver to the boot image but can't get up to the WinPE screen to enter the password, it just reboots at preparing network connections. Pressed F8 and checked there is no network card installed. Usiing the same driver that is in windows.smsts.log Originally added this driver a month or so ago for the older Surface pro's which worked good for them. WeSMSPXE.log have some new Surface pro 7's with I am guessing a new dock and now we have this problem. We had an older version of ADT which I have updated to 1809 today. I thought it might have better support for the dock.smsts.log I have one log from last week which should be ok we basically have the same issue no matter what I try. Added the smspxe.log as well in case its useful. Let me know if you have any ideas. :) Regards, Andrew
  5. Hi, I have a Windows 10 1607 image I configured and captured ages ago that I want to update to 1803. I thought I could use Scheduled Updates option to patch it up and I did install a number of updates into the image but it is still showing version 10.0.14393 (1607). Is there any way to offline service this image up to 1803 or am I going to have to recapture the image? Thanks in advance! Regards, Andrew.
  6. You should be able to just set the Internet FQDN on the Site System role for the SUP to a Public DNS record. For that to work you need split brain DNS so on the internal DNS server you set the A record to the internal IP and on the external DNS server you set the A record to the public IP.
  7. Well I've just found my own post googling for this information today.... At least I've helped someone
  8. Hi, I have just deployed a new SCCM Server which I am migrating an old deployment to. Getting a weird problem with the SQL Service Reporting Services where when I click on a report it takes me to a window in the root directory. This will keep looping opening more windows within itself. (See attachment) Any ideas?
  9. Well UEFI and Secure Boot seems to all just be working after only adding the UEFI paritioning step... Much easier than expected... They must have made it easier in the new version of SCCM or Windows because I couldn't get it going before.
  10. ok cool, thats easy enough. Any idea about supporting Secure Boot?
  11. Hi, I recently captured an image of Windows 10 and was able to successfully deploy it be utilizing the same TS for Windows 7 and just replacing the image file. With the new Windows 10 deployments though, I would like to be able to leave UEFI and Secure boot enabled in BIOS for new computers so we can take advantage of their features and also save some time with deploying computers. (Especially when users at branch offices need to configure this) So I am wondering what I need to do to utilize UEFI and Secure Boot? My Current Windows 10 TS looks like this: Only one partition step: So I guess step one I need the separate partition step for UEFI partitioning with variables defined in both to determine which partition type to use. I've seen some guides on that so I think I can add that in ok. What else might I need to do for UEFI and Secure Boot support? Thanks in advance, Andrew
  12. So this is fixed now, I added a bunch of the optional components to the new boot image (ver 10.0.14393.0) as well as a couple of network drivers and all seems good now.
  13. I read that I need to update the boot images I use for the TS. I checked and I see I have these new ones version 10.0.14393.0 so i assigned them to the TS but I get the error 8007002 as soon as I start the TS. Can't get logs cause command prompt isn't enabled in the new boot image, will enable and upload asap.... although when pxe booting it still seemed to grab the old boot image so I don't know whats going on yet. Obviously a bit of work I still need to do here....
  14. Hi, Been a while since I had to do anything to my environment but last week I finally updated SCCM 2012 SP1 to 1606. The update itself seemed to go pretty smoothly. We are finding that our Task Sequence stops at the Setup Windows and Configuration Manager step and won't install any of the applications/packages that are list in the steps after. I guessed that maybe the Configuration Manager Client Package had automatically updated to support the latest version so I have redistributed to all my DPs but still the TS stops after the Setup Windows and Configuration Manager step. The client seems to install fine as the agent is running and gets the client policy thats assigned. Here is the last part of the smsts.log Command line: "C:\WINDOWS\CCM\TSMBootstrap.exe" /env:Gina /configpath:C:\_SMSTaskSequence /bootcount:1 TSMBootstrap 8/03/2017 2:49:49 PM 1748 (0x06D4) Current OS version is 6.1.7601.1 TSMBootstrap 8/03/2017 2:49:49 PM 1748 (0x06D4) Logging successfully initialized. TSMBootstrap 8/03/2017 2:49:49 PM 1748 (0x06D4) Resuming Task Sequence in Full OS TSMBootstrap 8/03/2017 2:49:49 PM 1748 (0x06D4) No logging settings found in TS environement TSMBootstrap 8/03/2017 2:49:49 PM 1748 (0x06D4) Failed to get the environment key. TSMBootstrap 8/03/2017 2:49:49 PM 1748 (0x06D4) Failed to resume task sequence (0x800700EA). TSMBootstrap 8/03/2017 2:49:49 PM 1748 (0x06D4) Exiting with return code 0x800700EA TSMBootstrap 8/03/2017 2:49:49 PM 1748 (0x06D4) Process completed with exit code 2147942634 OSDSetupHook 8/03/2017 2:49:49 PM 1612 (0x064C) Task sequence completed 0x800700EA OSDSetupHook 8/03/2017 2:49:49 PM 1612 (0x064C) Waiting for command shell to complete. OSDSetupHook 8/03/2017 2:49:49 PM 364 (0x016C) Terminating system message loop. OSDSetupHook 8/03/2017 2:53:31 PM 364 (0x016C) Wallpaper has changed since initialization so it will not be reverted. OSDSetupHook 8/03/2017 2:53:31 PM 1612 (0x064C) Exiting SetClientProvisioningMode 0x00000000 OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C) Uninstalling Setup Hook OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C) Removing setup hook from registry. OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C) Successfully removed C:\WINDOWS\system32\OSDGINA.DLL OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C) Could not delete the file C:\WINDOWS\system32\OSDSETUPHOOK.EXE. Error code 5 OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C) Marking the file C:\WINDOWS\system32\OSDSETUPHOOK.EXE for deletion on Reboot OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C) Successfully removed C:\WINDOWS\system32\OSDSETUPHOOK.EXE OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C) Successfully removed C:\WINDOWS\system32\_SMSOSDSetup OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C) ::RegOpenKeyExW (HKEY_LOCAL_MACHINE, c_szSMSTSKey, 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,258) OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C) RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C) GetTsRegValue() failed. 0x80070002. OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C) End program: OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C) Finalizing logging from process 1600 OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C) Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\Logs OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C) Any ideas?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.