Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

mis@ypit.com's Achievements


Newbie (1/14)



  1. I had the same problem but I was unwilling to accept the concept of turning off secure boot. Eventually I found this TechNet blog post: https://blogs.technet.microsoft.com/configurationmgr/2017/04/14/known-issue-with-the-windows-adk-for-windows-10-version-1703/ The blog post has been updated with a download that has the problem files re-released with the proper digital signature. After following the directions in the included read.me file I was able to manually create the default boot images.
  2. Rocket Man's question 'what does it do' confused me for a while. A lot of the posts dealing with using OSDComputerName make it sound like the variable is baked in to SCCM and it 'just automagically' works. While searching around I found someone else who was having the same problem. This other person mentioned adding the 'set task sequence variable' AND setting it to %OSDComputerName%. Ah...is that what Rocket Man was talking about!?! I have never used variables in a task sequence before so I had no idea what actually needed to be done. This is what the OSDComputerName task sequence needs to look like:
  3. It looks just like the example in the guide. When I run the task sequence I get a prompt for OSDComputerName, enter whatever I want, and then the task sequence continues on its merry way. Unfortunately for me I can find no proof that the task sequence used the name I entered. My logs look just like the logs submitted by people showing an OSD that successfully used the variable.
  4. I forgot to mention that I used the same link you provided as a guide to set everything up. It is my belief that I have configured everything properly,
  5. SCCM 2012 R2 SP1 CU3 (5.0.8239.1403) Windows 10 Enterprise 1607 x64 CB (KMS Product Key) I am unable to figure out how to create a task sequence that deploys Win10 using OSDComputerName. Here is what I am doing: Create Hyper-V VM Install Windows 10 Run Windows Update System is NOT joined to a domain Use capture media and import as new OS image Create task sequence; I have tried moving around the 'Set Task Sequence Variable' but nothing seems to work PXE boot and run task sequence Enter something like 'OSDTEST' when prompted for 'OSDComputerName' The result is a system that joins the domain with a name like MININT-XXXXXXX. Other tidbits: There is nothing in the C:\Windows\Panther\Unattend folder. I believe there is supposed to be an Unattend.xml file there. My task sequence includes a few other customizations including installing the SCCM Client and a couple of applications. All of these other things work great. smsts.log
  6. I am encountering the problem where WinPE reboots after a few minutes while I am attempting to deploy an operating system. It looks like the computer I have needs a NIC driver added to WinPE. My real problem is that when I attempt to import the drivers this is what I get: Looking at DriverCatalog.log I see: Looking at SmsAdminUI.log I see: I asked a co-worker of mine to import the drivers I have and everything worked just fine for him. Any ideas on what might be going on would be appreciated. SCCM 2012 R2 SP1 CU1 running on Server 2012 R2
  7. We have been using an unattend.xml file created with Windows System Image Manager to create custom .wim files to deploy systems with a USB flash drive. I am attempting to use SCCM 2012 R2 to PXE deploy a custom OS but I am having problems translating our previous OS customization method into SCCM. Our current customization method is to start with a reference system, for example a Dell OptiPlex 9010, and use a Dell OEM Windows 7 DVD to start installing the OS. During the part of the OS installation where it asks you to enter a user name we hit CTRL-SHIFT-F3 and go into audit mode. We then install all drivers, updates, applications, and any desktop customizations we want. When we are finished we sysprep /oobe /generalize using an unattend.xml that includes "copy profile = True" to make the current administrator profile into the default profile. We then capture this system by booting to WinPE and running imagex. We can then use the .wim file with an installer disk to boot to a USB drive for OS installation. I have found many posts dealing with how to deploy an OS but very few on how to capture a custom OS image in the first place. For instance, I would love to be able to change the computer name, join to a domain, and install the SCCM client during OS deployment. Can I still use some of my previous method to create a customized .wim? Is it common to create custom .wim files for OSD or am I holding on to an obsolete method? Thank You Carl Sund
  8. I sometimes have a problem where the summary for an application deployment shows errors: ...but "View Status" shows this: Running a summarization does not help. Also, this is not a new deployment but one that is weeks old. I have been trying to find a report that would identify the systems that are having problems installing the application with no success. Does anyone have any suggestions?
  9. SCCM 2012 R2 I have this curious problem when deploying new versions of Java. When I add a new version of Java to my software library I select to supersede (and uninstall) the previous version. When I deploy the new version I limit the installation to when users are logged off. (So I can be sure there are no browsers open.) The behavior I am noticing is that while the new version is patiently waiting for the user to logoff the old version is uninstalled right away. If anyone else has noticed this behavior have you figured out a way to prevent the uninstall from taking place until the user logoff?
  10. I have all of those same parameters included in the transform file. A slight problem I have found is that different websites report conflicting descriptions on what EULA=? does. For example one site will say that EULA=0/1 means to not/accept the EULA and another site will say that EULA=0/1 displays/suppresses the dialog box for the EULA agreement. The default for EULA in the .msi file is EULA=0 so I originally tried using EULA=1...assuming this meant to accept the EULA. This did not prevent the first time use EULA notification. I then tried EULA=0 and had the same notification dialog on first run. I found references to AgreeToLicense but I am afraid that was a parameter for previous version of Java that has been discontinued. My theory is that each of these sites are reporting the truth for a particular version of Java and that Sun is actually flip-flopping around from version to version. Just to be clear....when you deploy Java 7.51 are you able to successfully suppress the first time EULA notification?
  11. I am trying to figure out the proper syntax for the command to deploy Java 7.51 with SCCM 2012 R2. Which is correct: msiexec /i "jre1.7.0_51.msi" transforms="ypit.mst" AgreeToLicense="Yes" /qn msiexec /i "jre1.7.0_51.msi" transforms="ypit.msi" "AgreeToLicense=Yes" /qn I have used Orca to create a transform file that includes EULA=1 but that does not seem to prevent the first time run popup for the EULA. I have been struggling with AgreeToLicense but I just can seem to get that to work either.
  • Create New...