Jump to content


Search the Community

Showing results for tags 'OSD'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests

  1. Hi everyone, I am working on a new TS after we have begun migrating from MDT 2013 to SCCM 2012 R2 v1511. The issue I have is that we want to be able to automatically rename machines based on the Device Affinity. I can import the machine into SCCM no problem... When it comes to my Task Sequence, I have setup a step called Gather based on MDT. I have then setup another step called Set Computer Name, this references OSDComputername and points to the Variable: %_SMSTSMachineName% This doesn't work and I end up getting the standard MIN_INT etc name. How can I resolve this? At the moment I am working on a Windows 7 image but I will also need to apply this to Windows 10 as well. I know as another resort, I can amend the Unknown Computers Collection - but I'd rather have it automated, as we'll be having our supplier send us a list of MAC addresses and Asset stickers which will be used to generate the name at the point where the machine is being built. Any help would be appreciated.
  2. Hi All, Can someone help me in setting AD Computer Description during the OSD ? I am using UDI for selecting OU during the OSD .Can I use the UDI for Computer description also ? Thanks in advance.
  3. Hi Guys, My environment is not integrated with MDT,I created a HTA file where tech can select the list of OU's(I have more than 100 OU's) during the OSD, I have added the hta file to run after the Disk partitioned . While testing i am not able to see the Front end ,i can see the log files(attached) Please let me know if any thing need to be setup in additional.Also help me in adding Computer description in the same hta file. smsts.log
  4. This might be completely outta bounds, but has anyone ever attempted image mgmt of android for tablets? We have a little less than 100 coming in and "they" want standardized OS across the lot and we would rather not do them all manually. Johan Arwidmark directed me to Kent Agerlund's blog and book on EMS, but I thought I'd present the question and see what if anything has been hacked together by the community. Thanks
  5. Hi All, We are currently setup with the following: SCCM 1606 and are in the process of developing our Windows 10 v1607 SOE and have currently run into an OSD Driver Install issue. We have packaged Dell CAB drivers for E7240, 9020 M/SFF/AIO and added them to an OSD task sequence. The task sequence completes the build, however we find that drivers are not installing. The SMSTS log shows the following errors (Please see screen dump) Our Windows 7 and Windows 8 OSD task sequences have been setup in the same way and we don't have any of these issues, it appears that it only affects Win 10 OSD deployments. Any thoughts?
  6. Hi Everyone, I found a great link on TechNet regarding information on Prestaged TS. The author even provided a TS ZIP that I was able to import " ConfigMgr 2012 Task Sequence to apply Prestaged Media to multi-partitioned BIOS & UEFI PCs"The last successful action in the TS was to shutdown Win PE. From there when you boot the PC back up it fails at writing to the drive. I was wondering if someone else could recreate the issue I am seeing or provide a solution if got it work? Thanks in advance Apply Prestaged Media for BIOS and UEFI PCs - CM12.zip
  7. Hello all, I hope I can lay this out clearly so someone can understand what's happening here and help out. We've had OS Deployment working for a couple of years now with no real issues. We have about 30 offices nation wide. We have a single Site and a Distribution Point at each location. The DPs are PXE enabled. They are all virtualized except two, which are located IN ADDITION to the primary DP VMs in our two largest offices. Both of these locations have multiple subnets. They both had speed issues on day one when we enabled OSD. After much troubleshooting and trying every suggestion we tried, we finally got "regular speed" by installing a physical DP on the subnet that the local IT staff were on. Two weeks ago we upgraded the WAN circuits in the 2nd office. We replaced the router and all switches. Because this location now houses our disaster recovery site, we rejiggered the network and added a new subnet that is now where all the clients are located. Now we have the same issue we had when we setup OSD. It took over 30 hours to image a single system. We have moved the physical DP to the new subnet, but PXE is not working now. I can get PXE working, so I'm really curious about the slow deployment across subnets in the same office. Our setup: HQ, 31 Subnets, virtual Site Server & DP, physical DP** on ITs subnet 31 remote offices with a single subnet and VM DP 1 remote office with 3 subnets a VM DP and a Physical DP** on client subnet ** Without 2nd DP imaging takes more than a day.
  8. Hello all, We’ve recently implemented SCCM (Current Branch) within our organisation. I’ve previously used SCCM 2003, but obviously some things have changed significantly! We’re having a similar issue to this post: https://www.windows-noob.com/forums/topic/12803-windows-10-enterprise-computer-name-problems-sccm-2012-r2-sp1/ When we deploy our Windows 10 image (1511 Education), we prompt for a computer name (stored in the OSDComputerName variable), however when the OSD TS completes, the machine is named WIN-XXXXXXXXX. I’ve examine the smsts.log file and can see the correct computer name listed within it and it applying to the unattend.xml file [updated C:\WINDOWS\panther\unattend\unattend.xml with OSDComputerName=13-0908-QGT204 (value was 13-0908-QGT204)]. We use the unattend.xml file to apply UK setting (language, keyboard, etc.) to our build. I then removed the “Use an unattended or Sysprep answer file for a custom installation” option from the “Apply Operating System Image” and redeployed the image again. This time the task sequence worked correctly and gave the computer the correct name. Within the xml file I can see <ComputerName></ComputerName> under the “component name="Microsoft-Windows-Shell-Setup"” section, which, I assume, is where the task sequence would update the name – in fact there are two entries, one for x86 and one for amd64 (we only use 64bit) – would this be the issue? Any thoughts or advice is welcome J Thanks, Jono
  9. Hello, We have a big problem for Dell Precision M6x00 models with two discs. We try to apply Windows OS on Disk 1 (mSATA) with the task sequence SCCM, but impossible! We have upgraded the BIOS version, same result ! A priori, the Disk 0 has priority over the Disk 1 in all cases Nothing in the BIOS proposes to change this state. Topics similary http://www.windows-noob.com/forums/index.php?/topic/10561-sccm-2012-r2-osd-fails-with-error-80070032/ https://social.technet.microsoft.com/Forums/en-US/297f9adb-d71d-445b-8fdf-9776b70c7b98/multiple-harddisks-and-apply-operating-system-image-failure?forum=configmgrosd have you got a idea ? Regards, MP. … The volume E:\ exists and is a local hard drive. The volume E:\ is using a valid file system. Windows target partition is 1-2, driver letter is E:\ !sSystemPart.empty(), HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\diskvolume.cpp,131) System partition not set Unable to locate a bootable volume. Attempting to make E:\ bootable. volume.getDisk() == iBootDisk, HRESULT=80070032 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installcommon.cpp,693) Volume E:\ is not on the boot disk and cannot be made bootable. MakeVolumeBootable( pszVolume ), HRESULT=80070032 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installcommon.cpp,772) Failed to make volume E:\ bootable. Please ensure that you have set an active partition on the boot disk before installing the operating system. The request is not supported. (Error: 80070032; Source: Windows) ConfigureBootVolume(targetVolume), HRESULT=80070032 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,499) Process completed with exit code 2147942450 !--------------------------------------------------------------------------------------------! Failed to run the action: Apply Operating System Image Windows 7 SP1. The request is not supported. (Error: 80070032; Source: Windows)
  10. Hi, I have a question regarding surface pro device firmware. We deploy Surface Pro 3s and Pro 4s at our entity. When a new driver/firmware pack is released from MS, we follow the usual instructions in downloading and applying the new driver/firmware pack to the devices. My question however is this- I noticed that if I run a manual windows update on either the surface pro 3 or pro 4, I see another system hardware update within the Windows update menu, when I know we have completed importing the newest drivers/firmware. Does anyone know why this is? I am guessing it is related to the touch panel itself, but I am looking to confirm. thanks.
  11. Hi, Our main site has multiple locations, and a few of them within the US support and deploy our images from the main office via SCCM 2012 R2 SP1 CU3. We have been troubleshooting some network issues recently, that I believe we have cleaned up now. However during some deployment testing, we are experiencing some inconsistent results that I hope someone may have an answer or idea of where to look. -Created 4 VMs setup for OSD (testing/troubleshooting) all of the VMs are set for PXE. -All machines boot up and get to the PXE menu and populate the available task sequences with no issues. -Our guy has reported that he started the same task sequence to all the VMs at same time manually, where they all will download the boot image as so, and move forward onto the imaging process. -Anywhere from 2 out of the 4, to 3/4 of the VMs startup just fine and run the task sequence to completion. The other 1-2 (depending on the test run, it varies) will reboot and then launch within winPE and start the task sequence. I could be wrong here, but I believe usually when a TS reboots it is because the boot image from the PXE or boot media differs from the boot image assigned to the TS which makes sense. Though, given nothing is different from one VM to the other, the TS is the same...which has me scratching my head. My other theory(keyword theory) is our user is experiencing this upon the boot up itself while downloading the boot image from the bios menu. VM 2 is requesting this boot image that maybe "busy" at that very second due to VM 1 requesting it as well, forcing sccm to use another available boot image? - more than likely wrong here, nor does that really make sense to me, I'm just picking straws at this point. Has anyone run into this, or seen it before? Any thoughts, things to try? Thank you
  12. Hi all, I'm in the midst of learning the OSD process that's handled by SCCM. My task sequence is using the default steps in order to minimise confusion / issues. The problem I'm facing is that during the disk partitioning steps, the C: partition isn't being set as active, so when the TS steps through to deploying the OS, it cannot find an area to put it. The key areas of the log are pasted below, but I've attached the entire log just in case. Any guidance would be thoroughly appreciated. Thanks in advance. ==============================[ OSDDiskPart.exe ]============================== OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Command line: "osddiskpart.exe" OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Reading partition size info for partition 0 OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Remaining size before partition: 256052966400 OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) size units: SIZE_MB OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Set partition size: 367001600 OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Remaining size after partition 0: 255685964800 OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Set an environment variable for partitions 0-1 without drive letter OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Reading partition size info for partition 1 OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Remaining size before partition: 255685964800 OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) size units: SIZE_PERCENT OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) 100% size specified. OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Remaining size after partition 1: 0 OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Set an environment variable for partitions 0-2 with drive letter OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Checking volume 'C:' for BitLocker OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Volume 'C:' is on disk '0l' OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Volume 'C:' is fully decrypted OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Checking volume 'D:' for BitLocker OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Volume 'D:' is on disk '0l' OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Volume 'D:' is fully decrypted OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Checking volume 'X:' for BitLocker OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) S:\ ffffffff OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) R:\ ffffffff OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Q:\ ffffffff OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) P:\ ffffffff OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) O:\ ffffffff OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) N:\ ffffffff OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Diskpart: select disk 0 clean create partition Primary size=350 assign letter=S format quick fs=ntfs label="System Reserved" active create partition Primary assign rescan OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Executing diskpart script: select disk 0 clean create partition Primary size=350 assign letter=S format quick fs=ntfs label="System Reserved" active create partition Primary assign rescan OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Command line for extension .exe is "%1" %* OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Set command line: "X:\WINDOWS\system32\diskpart.exe" /s "X:\WINDOWS\TEMP\DiskPartScript.txt" OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Executing command line: "X:\WINDOWS\system32\diskpart.exe" /s "X:\WINDOWS\TEMP\DiskPartScript.txt" OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Process completed with exit code 0 OSDDiskPart 02/06/2016 10:56:30 1176 (0x0498) Formatting partitions OSDDiskPart 02/06/2016 10:56:30 1176 (0x0498) Partition: 1 Primary OSDDiskPart 02/06/2016 10:56:30 1176 (0x0498) Partition: 2 Primary OSDDiskPart 02/06/2016 10:56:30 1176 (0x0498) Adding logical drive: C: OSDDiskPart 02/06/2016 10:56:30 1176 (0x0498) Adding logical drive: S: OSDDiskPart 02/06/2016 10:56:30 1176 (0x0498) Skipping non-local logical drive: X: OSDDiskPart 02/06/2016 10:56:30 1176 (0x0498) Formatting drive C: with NTFS filesystem, method quick OSDDiskPart 02/06/2016 10:56:30 1176 (0x0498) Start executing the command line: OSDApplyOS.exe /image:PPD00099,%OSDImageIndex% /runfromnet:False TSManager 02/06/2016 10:56:36 1100 (0x044C) !--------------------------------------------------------------------------------------------! TSManager 02/06/2016 10:56:36 1100 (0x044C) Expand a string: WinPE TSManager 02/06/2016 10:56:36 1100 (0x044C) Executing command line: OSDApplyOS.exe /image:PPD00099,%OSDImageIndex% /runfromnet:False TSManager 02/06/2016 10:56:36 1100 (0x044C) Command line for extension .exe is "%1" %* ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Set command line: "OSDApplyOS.exe" /image:PPD00099,1 /runfromnet:False ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Found run from net option: 0 ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Not a data image ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) ApplyOSRetry: ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) TSLaunchMode: PXE ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) OSDUseAlreadyDeployedImage: FALSE ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) 'C:\' not a removable drive ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Searching for next available volume: ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Volume S:\ size is 350MB and less than 750MB ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Volume C:\ is a valid target. ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Found volume C:\ ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Windows target partition is 0-2, driver letter is C:\ ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) !sSystemPart.empty(), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\diskvolume.cpp,130) ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) System partition not set ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Unable to locate a bootable volume. Attempting to make C:\ bootable. ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) bBootDiskDefined == true, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installcommon.cpp,690) ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Unable to find the system disk ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) MakeVolumeBootable( pszVolume ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installcommon.cpp,772) ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Failed to make volume C:\ bootable. Please ensure that you have set an active partition on the boot disk before installing the operating system. Unspecified error (Error: 80004005; Source: Windows) ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) ConfigureBootVolume(targetVolume), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,499) ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Process completed with exit code 2147500037 TSManager 02/06/2016 10:56:37 1100 (0x044C) !--------------------------------------------------------------------------------------------! TSManager 02/06/2016 10:56:37 1100 (0x044C) Failed to run the action: Apply Operating System. Unspecified error (Error: 80004005; Source: Windows) TSManager 02/06/2016 10:56:37 1100 (0x044C) smsts7.log
  13. Hi Guys, I've been building my Win10 image lately and for some reason SCCM refuses to complete any OSD Task Sequences successfully (on Win 10, or our old Win8.1 TS). It seems to be failing to setup the SCCM Client and then rebooting to a half built OS. smsts.log is here: https://pastee.org/7dkq5 I don't have a CCMSetup.log, it doesn't get that far. Any ideas? The key line that seems to stick out for me is: <![LOG[The action (Setup Windows and Configuration Manager) requested a retry]LOG]!><time="13:16:09.927-60" date="08-14-2015" component="TSManager" context="" type="1" thread="1260" file="engine.cxx:271"> <![LOG[Reboot to local harddisk]LOG]!><time="13:16:09.927-60" date="08-14-2015" component="TSManager" context="" type="1" thread="1260" file="engine.cxx:469"> I've been trying to work this out for the past few days now and I'm tearing my hair out Thanks!!
  14. Hey Guys / Niall - I'm currently using a fairly recent build of SCCM 2012 R2 SP1 CU3 which has MDT 2013 Update 2 installed. The task I'm working on now is creating an OSD Task Sequence which includes a UDI Wizard created using MDT. Currently, I am able to apply the task sequence to a system and have it complete without error - however - there are a couple of things which are not correct that I'm trying to figure out. I figured I'd post each to get opinions from others. Issue #1 - No Applications Installed (TS or UDI) Despite being added as a step to the TS or selected in the UDI Wizard, any/all Applications do not install. Packages which are listed in TS right after the Applications install just fine. Below is how I have my "Install Application" steps configured in the TS in order: Install Applications Group (No conditions) x2 Install Application step listing 5 apps. No conditions / not set to continue on error x3 Install Program steps (which work) "Convert list to two digits" step which runs "cscript.exe "%deployroot%\scripts\ZTICoalesce.wsf" /CoalescePattern:Applications /CoalesceTarget:CoalescedApps /CoalesceDigits:2" Install Application step which installs all with base variable name "COALESCEDAPPS" Install Package step which installs all with base variable name "PACKAGES" (don't have any packages configured in UDI - only apps) All apps listed are known to install successfully and log files shows them parsing, but never attempting installation. In fact, an AppEnforce.log file doesn't even exist once the build completes! Issue #2 - Reserved Partition Assigned Drive Letter Even Though Set Not To Do So This one isn't as big, but the 350mb System Reserved partition is assigned the drive letter D:. I went back and checked inside of the TS (and know I'm looking at correct step due to how partitions are named) and the partition has the option checked to not assign a drive letter. Below is how that step is configured: Format and Partition Disk (Conditions SMSTSMediaType not equal OEMMedia & SMSTSBootUEFI not equals true) Volumes System Reserved: Primary / 350mb fixed size / Make bootable / Do not assign drive letter / NTFS / Quick format Local Disk: Primary / 99% of disk / not bootable / assign drive letter / NTFS / Quick Format / Variable: OSDisk Windows: Recovery / 1% of disk / All options greyed out I'm not dead set on having the volumes configured this way - just basically need the OS to install to C:, have it be the only with a drive letter, and have it take up the most disk space - that's it. I'm collecting log files from a build this morning right now and can post them after generalizing them. Any suggestions? Thanks UPDATE I generalized, compressed, and have attached all log files from C:\Windows\CCM of build with these issues I ran this morning. Logs.zip Thanks!
  15. Hi Guys, I try to installl windows 10 (1511) with SCCM 2012 R2 SP1 with MDT2013 Update 2 over PXE. My problem is only one model (Zotak ZBOX ID83 Plus). All other PC'S (DELL, HP, Lenovo) work well. The TaskSequence Aborts by the step "Install Operating System". Network is all the time available The HDD is writable what i tried: - Import the Sata and Netword Drivers in the Boot Image - Bios Update - Format the HDD before OSD - Zero Touch installation (excluding MDT) - The SMSTsLog has no errors. The only way i found to install these Boxes, with an Standalone USB STICK and the ZeroTouch Task sequence. Thanks BoB
  16. Good afternoon, I have a windows 10 task sequence that lays down the OS nicely, installs all drivers, and activates windows/etc. We have kept fairly strict on standardizing the models of laptops/desktops that we purchase for our school district. We have a group of Lenovo T420 laptops that images perfectly with Windows 7 x86, but we just received a new batch and we're going to push Win10 x64 Professional to them. When getting the first one imaged, I noticed there were 4 or 5 drivers the task sequence did not take care of. I manually downloaded them, some of them only listed compatible with Windows 7 x64, but they worked fine with Win 10 x64, no issues whatsoever. I added those drivers to my sccm server, added them to my "x64 Lenovo Laptops" Driver Package, and updated them on my distribution point. I noticed when I right click the driver and go to the "Applicability" tab, it only had Windows 7 (64-bit) checked. I made sure Windows 10 Professional/Enterprise and higher (64-bit) was selected and even did 32-bit as well, applied, updated my distribution points, and I reran my OSD task sequence. Two drivers remain uninstalled after running the task sequence. 1) Base System Device, which is Ricoh PCIe SDXC/MMC Host Controller and 2) Intel® Active Management Technology - SOL I've double checked, readded the drivers to the packages/server, updated my distribution points and it does the same thing, only those two drivers WILL not install. What am I missing? Any help is appreciated, thank you!
  17. Hello, I need to create a prestaged image that I will store on a hard drive for our hardware vendor to have the image already applied on the computers when they arrived to our institution. Then the process will just continue with the rest of the task sequence steps once they arrive onsite. Can someone explain or point me to a written guide on how to accomplish this? Can the prestaged image be set to expire after x amount of time? Thanks in advance.
  18. I want to install Windows 7 Enterprise on a machine using SCCM 2012 OSD. The machine already has Windows 7 professional installed on it. The machine has 2 drives C: and D: created on a single HDD. I want to retain the user data on Drive D as it is. The size of data on D drive is huge, and I don't want to waste time backing it up and restoring the same on the same machine. I want to retain 2 drive structure. I don't want backup data on a USB (using Easy transfer or similar tool), not do I want to use USMT to copy D drive data on to a server share location. Any suggestions on how to go about it?
  19. I'm want to make a new task sequence to OSD, without MDT, but I wanna to avoid to have too many task sequence. Problem: each department has his own software but sometimes they are common in other departments. And then I have the OU's for each department. I'm going to try something like this: Goal: one single task sequence, instead of having 10 or 20... For software: declare a variable in a collection where that variable is something like "BundleSoftware_1 = true". In the task sequence, if this variable is true, then install the applications bundle; For OU's, I would do the same. A will declare the same variable for several collection (department A, department B, department C, etc). If variable = RH, then would match the step where it registers the computer in RH OU. I never did this, but I would like to know if anyone has setup something like this. Any other ideas would be great! Thanks in advanced!
  20. ixpnet

    OSD Reimage issues

    Hi All Credit to the author of this site, its fantastic knowledge. 1up! I have recently been tasked to re-image 45 PCs across several sites in the next 24 hours. I was hoping to run a unattended OSD (SCCM 2012 CU3) which would capture the PCName / Domain settings and apply our new (fat) image (55GB). Now I have captured the image that I want and I have created an OSD for my choosen collection. The OSD Deploys to the collection but I find that OSD is stuck at "Installing" status for the past couple of hours with a reboot in sight. I have used CMTrace on the old PC and Server but none of error relate to the time its was launch. The only error I had was network access account which has now been fixed. Please could someone offer some advice on what I should be looking for? Thank you ixpnet I have attached a couple of photo of my setup. Happy to upload logs if needed.
  21. Hi - I need some advice about where to search or what log to look at.... all of a sudden my Task Sequences for OSD are delayed in becoming available. For example: I deploy a TS to a collection but then when I boot, that TS isn't available for about a half hour and sometimes up to an hour. I have Googled Task Sequence logs, but I can't seem to find a log for just the process of deploying the TS to a collection, not the actual OSD itself. Any help would be appreciated. Jodi
  22. Hello, Is there any way to remove/hide/encrypt passwords appearing in clear text in the client-side logs during OSD? During OSD, i can read out domian, useraccount and password for the Client Network Access Account. This account have read on the packages share,and i dont want people deploying computers all over the world beeing able to read from the share. I think i read something about this in the realease notes for 1511, but i cant find it again. Hope someone else have done this, and can spare the time to give me the solution Best Regards Marius Senior IT-Consultant
  23. Hi! We have a number of computer models that we image with SCCM 2012 R2, and everything works just fine, apart from one model: Novatech nSpire 15.6 (yeah, the model is not descriptive, but that is the model name!) The laptop has standard Intel Haswell hardware, one fixed disk (Sandisk SSD) and an optical drive. This is much like other computers that we have in the organisation and we have no computers with two or more fixed disks When we image this particular model of computer, the task sequence fails at the "Apply Operating System Image". The partition map from the task sequence is: Volume 1: 350MB fixed size, NTFS Volume 2: 100% remaining space, NTFS The operating system is deployed to the "next available formatted partition" The SSD is partitioned and formatted successfully during the task sequence. If I disable this step and use diskpart for this, the task sequence still fails! Below is the point of failure, from the smsts.log file: User did not specify local data drive TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume C:\ has 336084992 bytes of free space TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume C:\ is not bootable TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume D:\ has 127548887040 bytes of free space TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume D:\ is not bootable TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume E:\ is not a fixed hard drive TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume F:\ is not a fixed hard drive TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume X:\ is not a fixed hard drive TSManager 15/10/2014 10:42:51 1292 (0x050C) TSM root drive = TSManager 15/10/2014 10:42:51 1292 (0x050C) We do not find an available volume to store the local data path TSManager 15/10/2014 10:42:51 1292 (0x050C) Set a global environment variable _SMSTSNextInstructionPointer=11 TSManager 15/10/2014 10:42:51 1292 (0x050C) Set a TS execution environment variable _SMSTSNextInstructionPointer=11 TSManager 15/10/2014 10:42:51 1292 (0x050C) Set a global environment variable _SMSTSInstructionStackString=10 TSManager 15/10/2014 10:42:51 1292 (0x050C) Set a TS execution environment variable _SMSTSInstructionStackString=10 TSManager 15/10/2014 10:42:51 1292 (0x050C) Save the current environment block TSManager 15/10/2014 10:42:51 1292 (0x050C) pszPath[0] != L'\0', HRESULT=80070057 (e:\nts_sccm_release\sms\framework\core\ccmcore\path.cpp,60) TSManager 15/10/2014 10:42:51 1292 (0x050C) Filesystem::Path::Add(sEnvPath, EnvDataFileName, sEnvPath), HRESULT=80070057 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,676) TSManager 15/10/2014 10:42:51 1292 (0x050C) Failed to save environment to (80070057) TSManager 15/10/2014 10:42:51 1292 (0x050C) TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\executionenv.cxx,842) TSManager 15/10/2014 10:42:51 1292 (0x050C) Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance. The parameter is incorrect. (Error: 80070057; Source: Windows) TSManager 15/10/2014 10:42:51 1292 (0x050C) SaveEnvironment(), HRESULT=80070057 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\executionenv.cxx,420) TSManager 15/10/2014 10:42:51 1292 (0x050C) Failed to persist execution state. Error 0x(80070057) TSManager 15/10/2014 10:42:51 1292 (0x050C) Failed to save execution state and environment to local hard disk TSManager 15/10/2014 10:42:51 1292 (0x050C) Any help in this would be greatly appreciated! -- Matt
  24. Hi, the build in report "User device affinity associations per collection" doesn´t list the "OSD Defined" relationships. We are using powershell to import computers and set the UDA relationship with the following command: Invoke-WmiMethod -Namespace root/SMS/site_$($SiteCode) -Class SMS_UserMachineRelationship -Name CreateRelationship -ArgumentList @($WksResourceID, 6, 1, $User) -ComputerName $SiteServer The console shows the relationship and software deployment works well. If we change the parameter "source" from "6" (OSD Defined) to "2" (Administrator Defined) the report lists the relationship correctly. Any ideas? Best regards
  25. Good Morning All / Niall - I'm setting up a Windows 7 x64 Pro OSD TS in a new 1511 environment and am stuck on something. I'm set up numerous OSD TS's before, but this is my first with 1511. Everything goes well until it gets to the step where the client is installed & configured where it stays there for probably 10-15 minutes. Eventually, it reboots then goes to the next step which still shows a message about the client on the 2nd progress bar then fails. When I log into Windows (after it reboots from the failure), the domain is joined and I may log in with domain credentials. I launch the SCCM Client properties in Control Panel and see that there's no site selected nor client certificate. I did find that if I manually enter the site code into the client under the "Site" tab, it immediately finds the site and connects to it. What I've Tried / Examined I've tried a few different things - all with the same results - including building a new client package from scratch using the steps in Niall's famous guides, and using in the task sequence; using the SMSMP string in the client properties of the TS, and examining log files. Even though I see a couple of errors in the ccmsetup.log, the client seems to physically installs fine and exits with code 0. When looking at LocationServices.log, I see a few things, though: In case the screenshot doesn't come through... Failed to resolve 'SMS_SLP' from WINS Unable to find lookup MP(s) in Registry, AD, DNS and WINS LSIsSiteCompatible : Failed to get Site Version from all directories Client is not assigned to a site. Cannot get site signing cert. LsRefreshManagementPointEx failed with 0x80004005 Client is not assigned to a site. Cannot refresh Local MP. Client is not assigned to a site. Cannot get portal info. The above loops amongst a few information messages Any ideas or suggestions to what this may be? I've got to get all of this working today! Thanks!
×
×
  • 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.