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. Currently working on a Windows 10 project , I want to get your input on how you distribute your image to the different departments: same image for all users , based on application security groups, or different task sequences for each department.Please share how you proceed and what do you recommend.
  2. I`m trying to capture a Win10 image with Office 365 but my TS is failing. The O365 application installs fine from Software Centre, but failing during OSD. I attached the SMSTS log smsts-20170718-132035.log
  3. Hi everyone. I'm hoping someone out there can assist. Sorry for the length post but my aim is to provide as much information as possible to eliminate any of the common gotchas. ConfigMgr is 1702 with latest Hotfix I've spent the better part of two weeks trying to figure out why OSD has all of a suddenly stopped working. It seems to have happened around the same we upgraded our last DC from server 2012 to 2016 (swing migration) and raised the domain fictional level from 2012 to 2016. From the many hours spent doing google kung fu, ConfigMrg should not have any issues working in 2016 etc. DNS, DHCP AD are all reporting healthy with the usual couple of things that we can ignore from the BPA (Best Practices Analyzer). How we do OSD: We exclusively image Unknown Computers and have done so for many years (Since 2012 R2). We do not image our machines using deployments to any other collection. We delete the computer from the SCCM DB when we need to re-image. This works well for us in our environment. :-) All Task Sequences are deployed to the Unknown Computer collection. We are using ADK 1703 (the most recent one with all bug fixes) and boot boot x86 and x64 boot images are distributed and enabled but we only use the x64 boot image. The issue: Machines can successfully PXE Boot into WinPE, all machines no matter make, model, physical or virtual) all get an IP address and we can ping the ConfigMrg server without any issues. Once a computer gets into WinPE the screen goes blank and the computer reboots straight away. Actions taken so far: Common gotchas I have checked: Checked the date and time are correct on the client Made sure to delete any unknown computers or any references to the machines I have been using for testing or imaging in general Thinking that it might possibly be a Boot Image/PXE related issue I followed a couple of very detailed guides online and removed the PXE role from the Distributions Points by: Unticking it from each DP, deleting the files in the Windows Temp folder, deleting the RemoteInstall folder, removing the Boot images from DP's, the usual reboots, checking logs, re-enabling the PXE roll on DP's rebuilding the Boot images, deploying the boot images, enabling the both x86 and x64 boot images, making sure that my Task Sequences were referencing the newly created boot images. I then booted a machine up (in this case a test VM) and pressed F8, I ran cmtrace and opened up X:Windows\Temp\SMSTSLog\smsts.log. Then I found this error message: There are no task sequences available to this computer.. Please ensure you have at least one task sequence advertised to this computer. Unspecified error (Error: 80004005; Source: Windows) TSPxe 12/07/2017 12:28:40 PM 1284 (0x0504) So I thought perhaps my Task Sequence deployments themselves might have some issue on the DP's. I tried redeploying the task sequences and creating a brad new Task Sequence to test and I still got the same error. I checked the boundary groups and Active Directory Sites and Services and everything looks fine. I tried initiating a discovery of everything possible. Here is an example screen capture video of the issue we are experiencing: Looking forward to any comments below!
  4. We are running into an issue with some brand new laptops that they are stopping in the middle of the task sequence with the error Page_Fault_In_NonPaged_Area. This happens at different times during the TS. Sometimes it is right after the Domain Join step when it is Initializing the SCCM Client. Sometimes it happens during the next step in our process, which is enabling .Net 3.5. I tried moving some of the steps around the TS to isolate the issue, but it doesn't seem to be a certain step causing it. We put one of our old laptops in the same collection and everything works fine. The new laptops have 8GB RAM. 4GB that came with it and 4GB that we added. We have tried with just one of the 4GB (tried with each of them by themselves) modules and the same problem. We have tried with SSD and HDD. Same problem using both types of drives. Any help would be much appreciated. Thanks! I have attached 2 of the smsts logs. smsts1.log is from the _SMSTaskSequence Folder in C:\ smsts2.log is from C:\windows\CCM\logs\ smsts1.log smsts2.log
  5. Hi, I created a USMT Restore task sequence and set to to restore the profiles that connected in the last 14 days. However when it runs it restores all the profiles, here is a Screenshot. Any idea ?
  6. Hi please help I'm pulling my hair out! After imaging a client with Windows 10 using SCCM and MDT integrated task sequence the region and language keeps defaulting to US region and language. I have altered the MDT unattended XML file to add EN-GB as this: SetupUILanguage> <UILanguage>en-US</UILanguage> </SetupUILanguage> <InputLocale>en-GB</InputLocale> <SystemLocale>en-GB</SystemLocale> <UILanguage>en-US</UILanguage> <UserLocale>en-GB</UserLocale> I have also added these to the customsetting.ini file: SkipLocaleSelection=YES KeyboardLocale=0809:00000809 UserLocale=en-GB UILanguage=en-GB SkipTimeZone=YES TimeZoneName=GMT Standard Time The image was captured with the UK region and language setting set for all users in Audit Mode. And still after deployment the language is set to US!!! I also get "something went wrong" before login after OSD. Any help would be much appreciated
  7. I've been having some trouble getting newly imaged computers to accept a new name during OSD using the "OSDComputerName" variable. First, some history...I had a fully working SCCM environment that worked perfectly with OSD. Then our cert authority's root cert expired, and everything went to hell. I had to rebuild SCCM and migrated/exported/imported all objects, including images and task sequences. That's where we are today. This is SCCM 1702 with full version 5.00.8498.1711, with MDT integrated (though I have 0 experience doing anything too complex with MDT). OSD is working, and for known devices the computer is keeping the computer name through use of the "_SMSTSMachineName" variable (see attachment sccm1.png) For Unknown computers, during OSD I am successfully prompted for the "OSDComputerName" variable, and I can plug it in just fine. The variable is part of the unknown computers collection (see sccm2.png). When OSD completes, the computer receives a "MININT-_______" name and not the name I've given it. On the old SCCM server, the computers would successfully accept the new name. This is the result in multiple task sequences (we have 3 copies of the task sequence...one for Win10, one for win7, and a win7 one with customization for a specific purpose). Per this article I have recreated the task sequence from scratch, but got the same result: https://social.technet.microsoft.com/Forums/en-US/a8d05720-946c-4960-b978-c517cb56310c/osdcomputername-not-working?forum=configmanagerosd I have NOT captured a new WIM, I may try that shortly, though I doubt it's the issue. The task sequence is deployed as "Available" and not "Required." We have a simple configuration with 1 site and 1 DP. I've attached an smsts.log file for one of these deployments. I don't even see acknowledgement of the computer name I entered when prompted (which begins with SEIU- )I'm totally stumped for next troubleshooting steps and would appreciate any feedback.smsts.log
  8. Hello, I was following below article for Windows 10 Upgrade Assessment. I have created Upgrade Assessment task sequence with steps to set custom TS variable on value of _SMSTSOSUpgradeActionReturnCode TS variable. https://deploymentresearch.com/Research/Post/533/Improving-the-ConfigMgr-Inplace-Upgrade-Task-Sequence My TS is setting custom variables (Message) depending upon the value assigned to _SMSTSOSUpgradeActionReturnCode . But what I observed is TS variable evaluation returns true only for _SMSTSOSUpgradeActionReturnCode = ‭3247440400‬ else returns false as per smsts.log even condition is matching. For example: 1) _SMSTSOSUpgradeActionReturnCode = ‭3247440400‬, set Message = No compatibility issues => Happening 2) _SMSTSOSUpgradeActionReturnCode = 3247440392‬, set Message = Compatibility issues => Not happening because evaluated to false. I confirmed by dumping TS variables to text file and found it _SMSTSOSUpgradeActionReturnCode = 3247440392 but still condition evaluates to false as per smsts.log. I have changed order of steps of setting TS variable, use of Dynamic Variable but outcome is same. I am using steps from below URL for setting custom message: Any help or thought to solve this puzzle is highly appreciated.
  9. Hi, I'm struggling to find a definative answer to a question. Is it possible to rebuild a machine via an OSD task sequence within SCCM 2012 R2? Is SCCM working correctly in that if I have previously built a machine via a task sequence, then try to rebuild that machine it does not see that same task sequence and therefore will not be able to be rebuilt? I have a sequence deployed to all unknown computers. The 1st time it builds fine, if I then try to rebuild, it will not see the task sequence. I am assuming as it's no longer an unknown computer. Part of the sequence places the computer in a specified OU, it seems that sometimes it will see the sequence, sometimes it will not. I am using a usb build key with not pxe boot server. Is it expected behaviour that you should delete the computer from SCCM and then rebuild, is there a work around to allow support staff who don't have access to SCCM to rebuild machines? Any help appreciated.
  10. Hi All We have upgraded to SCCM 2012 1702 with hotfix KB4019926 installed, everything seems to have installed fine. I am using the pre-production client which appears to be working a treat and turned my attention to OSD task sequences to test the new client on a build. The task sequence is ignoring the pre-production client despite the option "use pre-production client package when available" being ticked and instead installs the current production client. If i change the task sequence option to use the pre-production client instead of the production client it installs fine so the client does seem to work fine in OSD It just doesn't work if i leave the production client as the live client and tick the option to use pre-production client when available. Couldn't see anything in the logs to explain the behaviour Any help would be appreciated, thanks in advance
  11. I'm trying to set up a task sequence to deploy Windows 10 via PXE. We have SCCM 2012 SP2 CU4 running on Server 2012 (not R2), with WDS 6.5.9200.16384, ADK 10.1.14393.0, and MDT 6.3.8443.1000. It's s single site and single server. I'm building the image from the official v1607 Enterprise ISO in a VM, entering System Audit Mode and doing some minimal config, and then using a freshly-built SCCM Capture Media ISO to handle the sysprep and image capture. Once captured, I create a basic (non-MDT) task sequence and deploy it as available to the unknown computers group for media and PXE only. If I have the task sequence join the domain and install the Configuration Manager client, everything works fine. I end up with an inaccessible defaultuser0 account on the machine, but I can log in with a domain account and do what I need to do / give it to a user. However, if I have the task sequence not join the domain, then I can't log into the machine after the image is deployed. It does the specialize pass and then does the "checking for critical updates" step, reboots, and then it gets to a login screen for "defaultuser0" and I can't log in. I've checked on the source VM after another fresh build from the installation ISO, and the defaultuser0 account seems to get created as part of the Windows 10 Enterprise v1607 installation. Even if I delete this account before capturing the image, the defaultuser0 account shows up after deployment. (We do everything in system audit mode and do not create any accounts.) I've tried setting the options within the task sequence to enable the admin account and set the password, but it's still not enabled and I can't do anything. If I try restarting in safe mode or enabling the command prompt, the only account listed/selectable is "defaultuser0" and I can't log into it at all. I've also tried adding net user command line steps to the task sequence to add a new local user and add it to the local administrators group, but this causes the task sequence to fail with 0x00000002. The task sequence that doesn't join the domain also does not install configuration manager - this task sequences is for machines that will be off the domain and off the network and not centrally managed. My guess is these steps can't run in the WinPE environment, but I was unable to find any relevant info in the smsts log. If I could get the task sequence / capture media to trigger the standard OOBE, I think that would work fine for our purposes. But I don't know how I can do that. The capture media doesn't seem to have any options I can control for the sysprep step. Could I just remove the "Apply Windows Settings" step in the task sequence entirely to achieve the same result? Again, we're not using MDT because this is a simple, bare bones image and task sequence. Our goal is to PXE boot and install Windows 10 Enterprise with updates and a few applications pre-installed. For domain-joined machines, they get policy after booting into the OS and get all the other stuff that they get. For machines off the domain, all we need is access to a local admin account so we can log in and do a light touch config, depending on each user. If this isn't possible without MDT, then we'll look at creating the MDT packages and task sequences. Thanks.
  12. While I've been working with SCCM for over 6 years I have what's probably a "newbie" question. Is it ok to import drivers while current task sequences are running that deploy operating systems to clients? I won't be editing the task sequences just importing new model drivers (we do use auto apply). When I first started doing os deployments I made the mistake of editing a task sequence that was probably being used and it got corrupted. I don't want that to happen again thus my question now. In the past I've always been careful to import drivers only during change management windows and after I announced to our IT department that imaging was not to take place for a certain amount of time. Is this necessary?
  13. I've read some varying info on deploying applications using variables. What I'm trying to do is that lets day I have a machine name "PD-000001" and one named "EH-000001" i'd like to install a certain set of applications based upon the first two or three characters of the computer's name which indicates the department the computer is in. Anyone have any good reading on this or have done it? Thanks!
  14. Hello everyone! I have a few ready-to-deploy OS Task Sequences. They were tested and successfully deployed via SCCM (v.1606) already. And now I have the task to prepare these "OSD-TS"s for installation from USB drive. So the question is: do I have to create new TS, pointing the output to stand-alone media (the very beginning of "New TS Media" Wizard) or there is more quick way like just copy existing TS and "redirect" it's output to stand-alone media? Maybe some kind of PS script can help me? Thank you in advance.
  15. Hello, I'm having a weird issue with the HP 1030 G2 x360 laptop\convertible. When I tried to image it ,my TS failed to detect it as a Laptop, it turned out that it has a new chassis type 31. So I added the chassis type to the ztigather.wsf, however it still didn't detect the chassis type. If objInstance.ChassisTypes(0) = 12 or objInstance.ChassisTypes(0) = 21 then ' Ignore docking stations Else If not IsNull(objInstance.SMBIOSAssetTag) then sAssetTag = Trim(objInstance.SMBIOSAssetTag) End if Select Case objInstance.ChassisTypes(0) Case "8", "10", "11", "12", "14", "18", "21", "31" bIsLaptop = true Case "3", "4", "5", "6", "7", "15", "16" bIsDesktop = true Case "9" bIsTablet = true Case "23" bIsServer = true Case Else ' Do nothing End Select End if
  16. Hi guys, I'm actually struggling with a question. With Config Manager 1606, is there any way to have multiple boot images available, and be able to selct one during PXE? Regardless of all my attempts one boot image is automatically selected (the last distributed) I would be glad to read your ideas
  17. So I have been on version 1702 for a few weeks now and at the start of this week, the deployments have been failing when the os is starting to be deployed. I have made no changes to the task. On Monday I was told that it failed to image a desktop. I looked at the logs and saw the 80070002 error looking more there are other errors none of them make any sense. I have double checked the Network access account nad redistributed the os package. I have even tried and built a new TS still the same results. Please help. I have attached the log file. smsts3.log Edit: I have looked at other issues like this and none of the suggestions have worked.
  18. Hi guys, After developing my OSD process for my work and creating all my WIMs, the IT manager decided that it would be better for us to install the SCCM client and cache into a secondary partition in a hidden folder. Reason for this is we use DeepFreeze and the cache/config is getting wiped at thaw time and is causing problems with Windows Updates. I understand why, but it's creating quite a difficulty to implement. After a few hours of investigation I thought I had a solution. In the "Format and Partition Disk" step of the TS I have a 60GB Primary partition (SCCM Partition) created with no drive letter assigned, then the remaining disk space used for OSDisk. I did this because it was assigning C to the SCCM partition and wanted to install the OS to it. I thought if I used a diskpart command utilizing a txt file to assign M (the letter we settled on) to partition 1 of disk 0 (which is what diskpart told me it was) before the "Setup Windows and Configuration Manager" step, there would be an M drive for SCCM to install to, as per the installation properties I set, namely: smscachesize=40960 smscachedir="M:\SCCM\cache" ccminstalldir="M:\SCCM\client" I am getting no failures in the TS, and in fact nothing in the log files shows any failure except the normal ones you'll see regularly. The diskpart step is completing properly according to the smsts.log file. However, for some reason once the system finishes imaging there is no M drive, SCCM isn't installed and as a result none of the UDI-chosen software is installed either. There is no CCM folder anywhere to be found. The partition is visible in Disk Management, but has no drive letter assigned and if I assign it M there is no data in it. I'm really surprised that the step to install the client finishes without error and clearly didn't work. Thing is, I can't get a log file after that point to check because, once again, the SCCM files are nowhere to be found. I know I could do this by completely redoing the WIM I based everything off of, but that would take several days of work, and I'm about to leave on vacation for a week. Below are screencaps of the steps in question and a copy of the simply diskpart.txt file I'm using. Help please! diskpart.txt
  19. Is it safe to import drivers into SCCM during production hours? We're getting new models in this week and I've always imported drivers on the weekend after business hours for fear of corrupting current production task sequences. Am I correct in importing and creating driver packages only after business hours?
  20. My task sequences no longer prompt for computer name (OSDCOMPUTERNAME) allowing me to set that variable when the task sequence runs. Not sure where to go to restore this as it was. Any ideas?
  21. Hi, I've set up some task sequences which work great, however in our environment we have many servers that are attached to storage with Emulex HBAs, or LSIs. How do I ensure that I can target the volumes on my internal RAID card so that C is actually on the drive I want, ie volume 0 is volume 0 on my H700 RAID, not a 4TB drive on my Super Micro Array. Currently I just unplug external connectors so the volumes won't be seen during installation and then just plug them back in which works but isn't very elegant and there are times I would like to re-image a machine remotely using IPMI. My google searches aren't turning up much other than creating a user driven Task Sequence, but I like to just walk away after it kicks off. Is there a way to force WinPE to organize my volumes the way I want so that the first volume on my RAID card is drive 0? Also this is potentially catastrophic as I sometimes re-image production nodes in an existing cluster and this would result in the loss of important data. Interesting that I have to install the drivers for the emulex HBA before windows can see the volumes after server 2016 is installed, but apparently the WinPE image supplies the drivers which I never added to the MDT Boot image which surprised me. Thanks in advance for any help!
  22. HI Guys, so I have an issue that has had me stumped for some time now and im about ready to throw these tablets out the window. I have HP Elite x2 1012 G1 tablets, I can image them just fine using PXE or USB, and i know it works just fine (Im evening using one right now imaged that same way) I decided to make life difficult by opening one of these up, switching out the M.2 SSD with a larger 525gb Crucial drive. I have had a number of issues on it imaging with the crucial drive, Ive finally gotten to a point where it images and boots into windows 10, if I reboot, it comes right back up. but the minute I shut the computer down and turn it back on, it immediately gives me the error: "Recovery Your PC/Device needs to be repaired a required device isnt connected or cant be accessed Error code: 0xc000000f" now, i checked the BIOS settings and it does in fact see the crucial SSD. has anyone had an issue like this? OSD finishes, boots into windows, shut it down, turn it back on then it no longer sees the drives. something tells me it has to do with the UEFI stuff but Im not entirely sure at this point. hopefully someone has the answer to this, Im pretty sure im doing something wrong or missing something and of course if any more information is needed I can provide that. thanks in advance!
  23. Good day everyone, I would like to pick the brain of the proverbial community think-tank here on the forums. The product We are looking at purchasing a number of (what I am calling) WInBooks for students (Dell 3180's, Lenovo N22, etc). These are basically Windows 10 versions of their ChromeBook counterparts. 11" screens, Celeron/Pentium procs, 4GB RAM with 64/128GB SSD's...and wireless only. The IDEAL solution Generally speaking, I think the solution to provisioning these would be using InTune, but that is not on the table due to budgetary reasons. As such, I do not have CM setup as an MDM. The more likely solution Use WICD and create a provisioning package that we apply when the new laptops are first turned on...apply SharedPC settings, wireless profile, domain join, etc. The concerns/problems We like to image things that come in for a number of reasons...cleans off bloatware from the mfg's, install organizational specific software, customize other settings, etc...however, with most of these devices only having wireless cards and no dedicated NIC, it takes a couple more hoops to jump through in order to image them (currently just using a USB drive). Using WICD to create a provisioning package that we apply at first boot is the simplest solution, but it leaves all the mfg's software installed, as well as trial software that gets in the way. Using a USB drive for OSD gives us a clean laptop and software we want installed, but still leaves us needing to do something about the wireless profile and domain join. Theorycrafting My initial thought was to use DISM to apply a provisioning package(s) at various steps in the TS in order to try and automate the process via TS. For example, first apply a package with the wireless profile immediately after the image is applied, and then during the software installs, apply another package with the domain join (no idea if this would work yet, as I have yet to test it)...this would be contingent upon the wireless profile being applied first, and actually connecting to the network during the Install Applications portion of the TS...and I have no idea if that would work. What else should I take into consideration? Has anyone else dealt with something similar? Perhaps there is a more simple solution that I am missing (can't see the forest for the trees)? All input is appreciated! Thanks!
  24. Hello all. During OSD my task sequence is failing with error code 0x80004005 at the very end of "Apply Operating System". The attached smsts.log (smtsprobook) seems to indicate something funny going on with partitions? Test Systems: 1. HP Prodesk 400 G3 SFF 2. HP Probook 430 G3 History: I have created a task sequence for deploying Windows 7 Enterprise X64 w/ SP1. This task sequence works great for the HP Prodesk. No issues at all. Task Sequence Steps (in order): Capture Windows Settings Capture Network Settings Install Operating System Restart in Windows PE Format and Partition Disk Apply Operating System Apply Windows Settings The rest doesn't really matter since the task sequence is failing at "Apply Operating System" (On the HP Probook 430 G3) This issue only occurs on the Probook (laptop) and NOT the Prodesk (desktop). The way we are managing OSD here at my company is to have a "Golden" Task Sequence, then just copy that same task sequence for as many different model of systems we have and insert the corresponding driver package as well as rename the task sequence for whatever new model we discover we have or receive. So we received our new shipment of Probooks (laptops) and I did what I always do when we get a new model. I grabbed the Windows 7 drivers for it (Note: These systems come with Windows 10 installed. Our image is Windows 7 Enterprise x64 SP1.) and created/copied a task sequence for the new model by simply switching out whatever driver package was in the task sequence that I just copied with the correct package for that model (a lot of this is irrelevant since again, the task sequence is failing at "Apply Operating System" before it even tries to install drivers.) Things I Have Done: Made sure all content called for in the task sequence is on the DP Deployed the TS as Available (PXE,Media,Blah blah) to All Unknown Computers Read through the provided smsts.log and could not make sense of it. Seems error 0x80004005 is a "beat around the bush" error Created a task sequence from scratch then tested. Still same issue at the same place Thought maybe its an issue with my .wim but I dont think so as this has worked on some of our other models tested Came here for help I am at a total loss as of where to start to troubleshoot this error. Most of the info you will need to help asses the issue is probably contained in the log(CMTrace it). Please let me know of anything I left out that could help. Thank you! smtsprobook
  25. Hi Apologies if this is the wrong place for this question, I have seen/used the great PowerShell scripts for documenting my SCCM setup. but I was wondering is there anything out there similar for generating a Image build release note. i.e. all the apps installed, O/S etc etc, ideally in a nice presentable format. Thanks Rob
×
×
  • 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.