Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About bighoppa

  • Rank
  1. Attempting to build a TS to upgrade our various Win10 machines to 1703, but when I try to go through the Add Operating System Upgrade Wizard it fails when adding the path to the extracted install files. I've tried pulling the files from a couple of different ISOs of 1703, and just keep getting this error message. I've ensured the permissions for the logged in admin account as well as the machine account to the 1703 directory are set to full. I even tried pointing it to an ISO, but that obviously failed to. Any help? Does it matter that the install file under Sources on the ISO is an ESD now instead of a WIM? Oh, should probably also mention my PSS is on separate hardware from my DP, but didn't think it would matter as long as the path was correct.
  2. Never mind. Don't need to set TS variable in the TS when you set it before execution. At least not when MDT is integrated. That's the only thing I can think of that is different between environments. OSDComputerName gets applied just fine during Apply Windows Settings without additional intervention.
  3. This should be easy. I've done it dozens of times, through CM2007 and CM2012R2. Now, with CB, my brain isn't working. Environment variable OSDComputerName created on Unknown Computers collection and no value assigned - Check! TS step Set Task Sequence Variable after Apply Operating System Image with Variable: OSDComputerName and Value:%_SMSTSMachineName% - Check! TS Prompts me for OSDComputerName value prior to starting up and I enter it - Check! OSDBackground pops up and there is my OSDComputerName value on the screen - Check! During deployment, after rebooting, OSDComputerName changes to MININT-XXXXXX, and the value I input when starting the TS is overwritten. This tells me that _SMSTSMachineName is overriding OSDComputerName instead of vice versa. Looking back at the TS in my old 2012R2 environment I have the Set Task Sequence Variable step set the same way. Where have I gone wrong?
  4. Solution is to delete the deployment, delete the package, go into C:\SCCMContentLib\FileLib\ and delete the offending directory (099F in this case), re-download the Software Update Group content, re-create the package. The package distributed to all three DPs normally and I was able to deploy the updates to my testing group, and thus deploy them on time tonight.
  5. For some reason this month I'm getting this error message when I try to distribute a newly created update package to our three DPs (one local, two remote). The DPs all have 200gb+ of storage free, so space is not an issue. The CM Primary machine account has full control on the shares and the source directory. I wiped the deployment and the package, re-downloaded the updates from the update group and created a new package. The package creates fine, but then fails to distribute content to the DPs. If it were a disk issue - either a failing drive or space - I would think it would only be one of the DPs that fails, but it fails on all three. I tried creating a new share for updates, re-creating the permissions, and creating the package there for deployment. Same issue. The distmgr log shows the package being created, snapshots being taken of all the content, then a big error block: Watching the console after the package contents were downloaded and the wizard completed, the package shows up green, 100% compliant distributed to all three DPs. After the MoveFileW error block shows up, the package goes red with 0% compliance and content status shows Distribution Manager failed to process package. Any help is greatly appreciated.
  6. Possibly unrelated, but 4022 wasn't enabled in the local firewall of the secondary site server. Database replication also had not completed, so maybe that was a cause. Regardless, this morning the secondary site is allowing me to add credentials to push the client, and machines are getting client installs properly.
  7. I've got an instance of ConfigMgr 1703 running to replace our old 2012R2 site, and we have six offices in other locations we need secondary sites for so we don't have a lot of MP and DP traffic across the WAN. I successfully provisioned the first secondary site this morning, but now I am trying to set the Client Push installation settings and when attempting to specify the service account, I get the attached error message. Once this pops up it crashes my ConfigMgr console, and it happens on my local workstation, my primary site server or the remote MP. Any ideas where to start troubleshooting this issue? I used the same account on the Primary site server for client push installation and it worked fine. Push works within the local site, but obviously fails at the remote site.
  8. Great stuff as always. Thanks for your efforts. I'm getting this error when I try to install 1606 on Server 2016 with SQL 2016 from your powershell script: I've stepped back through the setup, roles, prereqs, etc. and can't find the issue. The ConfigMgrSetup.log section where it fails has a lot of INFO: SQL blah blah entries, but everything looks OK in SQL as far as I can tell. Google and Bing bring up nothing remotely close to that error message. Any ideas? Thanks in advance. Edit: Hmmm...Software Assurance? My keys are correct...
  9. I'm running into the same issue as edie. The trick is, I'm not using an unattend.xml, just the task sequence. SMSTS.log isn't any help, either, since it ends showing no errors. I tried creating an unattend.xml and editing out the Windows Shell entry from the specialize pass, but the same error shows up. Any leads?
  • Create New...