SCCm 2012 OSD Sysprep Failure
Benny.Script replied to Benny.Script's topic in Configuration Manager 2012But that's odd to me because the drivers install and WinPE isn't even in play anymore. The OS kinda installs and sysprep kicks off but it fails because the C:\Windows dir isnt even there. -OS installed and client running on ref computer -Client gets TS -Reboots into WinPe -Partitions Disk -Installs OS (used .iso from media) -License/Admin/Join Workgroup -Apply Lenovo Tx20/Tx30 series drivers (pkgs) -Install/Configure SCCM Client -Prepare Client for capture -Sysprep <---Fails out So how can it not get a NIC Driver after it installs the client from the MP? If there are any more logs you want to see I took the Logs dir We are not doing a migration, full rebuild, if there is a way to save the WIMs that'd be awesome!
SCCm 2012 OSD Sysprep Failure
Benny.Script posted a topic in Configuration Manager 2012I have an issue with OSD Captures in 2012, since we cant import 2007 wim files. The computer will init the TS and go through all of it except the sysprep portion. That fails out. I have the logs from the client with some very non descriptive errors. The OS install doesnt look like its done before sysprep kicks in. smsts.log smsts-20140812-162414.log
Package Deployment keeps failing
Benny.Script posted a question in Deploy software, applications and driversI get the error below when trying to update the package on the DPs. The servers have enough disk space, there are no users trying to get to that dir (xxx0015c), and the name is under 128 chars. I have beaten my head against a wall for too long trying to figure this issue out. This happens with another package that i have too, so this isn't the only one. any ideas SMS Distribution Manager failed to copy package "xxx0015C" from "D:\Shared\source\SAPOfficePlugin\" to "MSWNET:["SMS_SITE=xxx"]\\xxxFS\SMSPKGD$\xxx0015C\". Possible cause: SMS Distribution Manager does not have sufficient rights to read from the package source directory or to write to the destination directory on the distribution point. Solution: In the SMS Administrator console, verify that the site system connection accounts have sufficient privileges to the source and destination directories. Possible cause: The distribution point might not be accessible to SMS Distribution Manager running on the site server. Solution: If users are currently accessing the package files on the distribution point, disconnect the users first. If the package distribution point is located on a Windows NT computer, you can force users to disconnect by clicking on the "Disconnect users from distribution points" box in the Data Access tab of the Package Properties dialog box. Possible cause: The distribution point does not have enough free disk space to store the package. Solution: Verify that there is enough free disk space. Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.