anyweb

they are not downloaded, look at the download column, the list of updates in the configmgr console is just an index of those that are available so no problem, you can customize the servicing plan to look for the language you want, eg: Feature update to Windows 10 Enterprise, version 1607, en-us

have you tried plugging it in to a different USB port ?

from the logs you emailed to me, here's your problem Setting the custom destination variable 'Drivers' to 'C:\_SMSTaskSequence\Packages\' it should be Drivers01 as per the blog post (step 6), read it again and follow it exactly.

ok those two logs don't give me enough info, the smsts.log (not the good one...) is missing most of the info we need to see the real failure, the log has probably rolled over, you need to increase the size of the smsts log file in windows.... try this.... Create a new Run Command Line action as the first action in the task sequence by clicking Add / General / Run Command Line, in the new Run Command Line action, set the name to Change CCM Logging options and then add the following command line: cmd /c REG.exe ADD "HKLM\SOFTWARE\Microsoft\CCM\Logging\@GLOBAL" /v LogLevel /t REG_DWORD /d 0 /f & cmd /c REG.exe ADD "HKLM\SOFTWARE\Microsoft\CCM\Logging\@GLOBAL" /v LogMaxHistory /t REG_DWORD /d 3 /f & cmd /c REG.exe ADD "HKLM\SOFTWARE\Microsoft\CCM\Logging\@GLOBAL" /v LogMaxSize /t REG_DWORD /d 5242880 /f do that capture the new smsts.log (or smsts*.log), email the logs to me and let's see what they tell me

can you attach the smsts.log file please

Introduction If your users are complaining that they cannot enroll devices or are having related issues you should do some initial troubleshooting, and one of those things you should check is the Service Health of the Microsoft Intune service to verify that the issue is not a user or configuration issue, but how do you do that ? Intune Preview health status In Intune Preview, click on any of the blades (apart from the Access Control, Manage Users and Open Classic Intune Portal blades) in the Intune dashboard, for example click on Manage Apps highlighted in red below Click on Help and Support And then click on See the current status of the service link on the right pane This will bring you to the Office 365 Service Health page, which will list the service health status of the following: Office 365 Portal Azure Identity Protection Identity Service Microsoft Intune and if any problems are detected you’ll get a report of what those problems were, in this particular case we can see there are no issues with Microsoft Intune, however the Office 365 Portal has some issues with reports. You can also click on the View History link (top right) to get more info about what’s been happening in the last 30 days. Or use the search field to search for say Microsoft Intune or click on any found Id, to get more details Note that the Intune classic portal, has a link to check for Service Health, under Admin, Overview, but it will link you back to the Office Portal as described here. Recommended reading https://blogs.technet.microsoft.com/enterprisemobility/2016/12/07/public-preview-of-intune-on-azure/ https://docs.microsoft.com/en-us/intune/whats-new/whats-new-in-microsoft-intune cheers ! niall

can you include the smsts.log pls

hi, i can teamviewer in if you have that possibility, then pm me with the details

why Windows 7, if the device is UEFI i'd recommend Windows 10 (or at least Windows 8.1 with update), must you install Windows 7 on it ? normally the only way to get Windows 7 to work with uefi is to enable a CSM mode in the bios to disable Secure boot.

well the process must be started in Windows, that's where you get the GUI to enter the capture destination details, the credentials needed, details about the image and then it SYSPREPs the machine before rebooting and starting the capture process in WinPE, please ask your trainer to review the steps again (in particular step 3) to see how that occurs,

this chart is updated via the Service Connection Point role (which checks weekly) In online mode: Diagnostics and usage data is automatically sent once a week from the service connection point to the cloud service.

did you try his advice ? To create/remove a NAP policy for software updates, you must select Enable/disable NAP evaluation on the NAP Evaluation tab in software update properties. Therefore I browsed to Software Library -> Overview -> Software Updates -> All Software Updates and added the Column "NAP Evaluation". I sorted these criteria and saw that there were a couple of old updates haven set a date instead of "No". After selecting them, I unchecked "Enable NAP Evaluation" in the NAP Evaluation tab of the properties and tried the prerequisites check again. Success!!!

sorry for the delay in responding i've been busy, do you have time to do this over teamviewer with me so i can take a closer look?

well Cireson do a lot of SCSM, have you checked them out ? https://www.cireson.com

doing osd over wireless is not recommended as the the connection could drop or certificates can not be reached, also you cannot PXE from wireless so that would limit you to starting the task sequence in Windows, i'd suggest you look at the lenovo usb network adaptors instead cheers niall

IntroductionMicrosoft have released a new version of the ContentLibraryCleanup tool for System Center Configuration Manager in the latest Technical Preview release (TP1701). By upgrading your Technical Preview release to version 1701 you can start testing the new features of the tool today, and some of these new features have been requested on UserVoice, a forum where people can ask for changes to a product, get others to vote their idea up, and if enough interest is seen, to fulfill a need. About the toolThis tool first surfaced in Technical Preview 1612. It’s designed to find content that is broken in one form or another on your distribution points (for whatever reason) and to alert you, or to free up space by deleting that broken content. It was designed to be cautious, if it doesn’t know exactly what is going on it will quit rather than accidentally delete files. Note: The tool is currently in Technical Preview so avoid running it in a Production environment. You can run the tool from the Primary site, or if speed is important, run it from the distribution point you are targeting. In fact, you can run the tool from anywhere that can do remote WMI calls to the provider/Distribution Point and SMB calls to the Distribution Point. It can be found in the following location (after you’ve installed the latest Technical Preview release), where <driveletter> is the drive letter that you installed ConfigMgr on: <driveletter>\Program Files\Microsoft Configuration Manager\cd.latest\SMSSETUP\TOOLS\ContentLibraryCleanup Note that you’ll need appropriate access to the cd.latest folder, so press Continue in the UAC prompt. What switches does it use ?By opening that location with a command prompt and typing the following command: ContentLibraryCleanup.exe /? you can see the following output: Usage: ContentLibraryCleanup.exe [/delete] [/q] /dp <Distribution Point FQDN> [/ ps <Primary Site FQDN> /sc <Primary Site Code>] [/log <log file directory>] /delete (optional) — delete the content, do not print what would be deleted. /q (optional) — run in quiet mode. Suppress all prompts (assuming delete mode) and do not open log file automatically. /dp <Distribution Point FQDN> (required) — the FQDN of the target distribution point. /ps <Primary Site FQDN> (optional*) — the FQDN of the primary site. *Required if the distribution point is on a secondary site. /sc <Primary Site Code> (optional*) — the site code of the primary site. *Required if the distribution point is on a secondary site. /log <log file directory> (optional) — the directory to place log files in. Can be a network share. If not specified, the temp folder is used. Note: By using the /q switch, this also assumes you answer ‘a’ to deleting all found orphaned content in conjunction with /delete. Testing the toolSo let’s test it. Note: Make sure to login as a user with Full Administrative access to the distribution point and with the Full Administrator RBAC role (this version of the tool doesn’t check if you are in an ADSG, so make sure you are explicitly a Full Administrator). Enter the following command (replace the FQDN in bold with your dp FQDN and replace the log folder location with your chosen location): ContentLibraryCleanup.exe /dp cm02.windowsnoob.lab.local /log d:\ContentLibraryCleanupLogs when prompted about what-if, answer y for yes. Notice that it tells you how much space it would have saved it you had run it in delete mode. Running the tool also automatically opens the logfile in CMTrace and that log file will give you details about the following Orphaned packages Packages with invalid contents Orphaned files Bytes freed if the tool is run in delete mode Using the /delete switchNow that you are familiar with the tool it’s time to use it for what it was designed for, so we’ll add the /delete switch. Note: In the example below, there is NO problem on the distribution point, so no space is available to be freed up. Enter the following command, notice the /delete switch. Please replace the FQDN in bold with your distribution point FQDN and replace the log folder location with your chosen location: ContentLibraryCleanup.exe /delete /dp cm02.windowsnoob.lab.local /log d:\ContentLibraryCleanupLogs answer yes to see the results and you’ll get a dated log file with the details of what was freed on the dp in question As there was no problem on this dp, no space was freed. Deleting Orphaned contentSo the above shows what happens when there’s no problem on the dp, but what if there was one or more orphaned files or packages ? Note: In the example below, there is a problem on the distribution point, so we can free up space. Let’s see the results of that….in the first check we omit the /delete switch, to see that it correctly identifies the problem, and it does! next, it opens the log file (which auto-opens) Next, run the command again but this time add the /delete switch, the red downward pointing arrow points to the orphaned content and prompts you what to do with it… answering yes to the prompt will delete the orphaned content (or answer a to delete all), and, now you can see a difference in the log file too… Result ! Hopefully this new improved tool will help you clean up any unwanted content on your distribution points, and it’s a great improvement and proves that UserVoice works ! thanks to Brandon @ Microsoft for answering my questions ! cheers ! niall

do you mean for the background image as in WinPE ? or duing the OSD process...to customize the background images used during OSD simply locate the files in MDT2013\Toolkit\Tools\x86 folder, you should see some STEP_01.bmp and so on, to customize the wallpaper simply right click on your MDT created boot image and change it on the customization tab

welcome to the forums and please tell your friend thanks from me

so many questions, it's best to take things one problem at a time, i can do teamviewer with you later this evening if that works, if not then tomorrow sometime, let me know via PM cheers niall

well XP is not supported by Microsoft anymore so I can't imagine why you would be capturing it, but does the smsts.log file reveal anything ? the error means. The specified procedure could not be found. Source: Windows -----

if you add a restart computer before displaying that udi does it help ?

welcome to the forums, i'd highly recommend you get some training if at all possible, just to be sure that you don't do something you'll later regret :/ cheers ! niall

so what exactly do you see when you pxe boot, can you take a screenshot of the error, is it happening on only one system, is there a network cable attached ?

have you configured a dhcp server ?

can you check what the ConfigMgrPrereq.log in the root of C: on your ConfigMgr server says about the error ?