Jump to content


Search the Community

Showing results for tags 'Windows 10'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • 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
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • 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


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 96 results

  1. Hi, I have a device that is in SCCM and has multiple TS deployed to it. Although when i try to PXE the machine it aborts as it cant find any advertisements. I've checked the SMSPXE.log file and it see's that its trying to PXE but has no advertisements deployed to the device. Any help would be great!
  2. as you can see on this Picture. my CB is telling me 1511 upgrades are available and my CBB is telling me 1607 are. can someone explain to me why that is? cause in my head it should be the other way around.
  3. Our Windows 10 Enterprise PCs were getting updates directly from the Internet saturating our pipe. To stop this behavior we had to block a range of WindowsUpdate IP at the firewall but later just stopped the Windows Update service on every Windows 10 1607 PC. We are using SCCM 1610 (WSUS installed same server) - Windows 7 PCs not a problem just Windows 10. By doing an RSOP to a workstation, the Specify Intranet Microsoft Update Service Location points to http://server.contosto.com:8530, our GPOs are the following: Administrative Templates/Windows Components/Windows Update/Defer Windows Update/Defer Select when Feature Updates are received - Enabled - 180 days Administrative Templates/Windows Components/Delivery Optimization Download mode - bypass Under Settings, Choose how updates are delivered - When this is turned on, your pc ... that settings is gray out, PCs on my local network and PCs on my local network and PCs on the Internet nothing (no option selected.) How do you stop from Windows 10 1607 to get updates to the Internet? What am I missing? That shouldn't be the behavior, we like to control when updates are delivered.
  4. Everyone, I've been on a mission to get a wireless task sequence working off of a USB jump drive/Stand-alone media OSD scenario, and i'm 99% there. I still have some long-term tweaks, but I am pretty pleased with it so far. The only thing I cannot get going is the computer rename script I have that works FLAWLESSLY over the wire, but since i'm having to join the wireless profile at the end of the task sequence I have to put the Gather/rename script there as well since it pulls our computer-name prefix based on gateway/site IP. This is all done through a custom customsettings.ini file on the gather / process rules step. The task sequence ends successfully, but the computer is not renamed. I look at the smsts.log in windows\ccm\logs and it shows where it goes through my gather phase and computes the OSDComputerName correctly, but it doesn't rename it. It then seems to finish the gather step and move on to my domain join step and eventual reboot/task sequence being completed, successfully. Here's the end of the log: Using COMMAND LINE ARG: Ini file = MPS-Rename.ini InstallSoftware 1/31/2017 4:07:02 PM 3820 (0x0EEC) Finished determining the INI file to use. InstallSoftware 1/31/2017 4:07:02 PM 3820 (0x0EEC) Added new custom property MYLOCATION InstallSoftware 1/31/2017 4:07:02 PM 3820 (0x0EEC) Added new custom property MYSERIAL InstallSoftware 1/31/2017 4:07:02 PM 3820 (0x0EEC) Using from [settings]: Rule Priority = MODEL,SERIAL,DEFAULT InstallSoftware 1/31/2017 4:07:02 PM 3820 (0x0EEC) ------ Processing the [20DL0079US] section ------ InstallSoftware 1/31/2017 4:07:02 PM 3820 (0x0EEC) ------ Processing the [sERIAL] section ------ InstallSoftware 1/31/2017 4:07:02 PM 3820 (0x0EEC) Property MYSERIAL is now = MP1368SR InstallSoftware 1/31/2017 4:07:02 PM 3820 (0x0EEC) Using from [sERIAL]: MYSERIAL = MP1368SR InstallSoftware 1/31/2017 4:07:02 PM 3820 (0x0EEC) ------ Processing the [DEFAULT] section ------ InstallSoftware 1/31/2017 4:07:02 PM 3820 (0x0EEC) ------ Processing the [10.80.16.1] section ------ InstallSoftware 1/31/2017 4:07:03 PM 3820 (0x0EEC) Property MYLOCATION is now = MPHS InstallSoftware 1/31/2017 4:07:03 PM 3820 (0x0EEC) Using from [10.80.16.1]: MYLOCATION = MPHS InstallSoftware 1/31/2017 4:07:03 PM 3820 (0x0EEC) Process completed with exit code 0 InstallSoftware 1/31/2017 4:07:03 PM 3820 (0x0EEC) Property OSDCOMPUTERNAME is now = MPHS-MP1368SR InstallSoftware 1/31/2017 4:07:03 PM 3820 (0x0EEC) Using from [DEFAULT]: OSDCOMPUTERNAME = MPHS-MP1368SR InstallSoftware 1/31/2017 4:07:03 PM 3820 (0x0EEC) ------ Done processing MPS-Rename.ini ------ InstallSoftware 1/31/2017 4:07:03 PM 3820 (0x0EEC) Remapping variables. InstallSoftware 1/31/2017 4:07:03 PM 3820 (0x0EEC) Property TaskSequenceID is now = InstallSoftware 1/31/2017 4:07:03 PM 3820 (0x0EEC) Property DeploymentType is now = NEWCOMPUTER InstallSoftware 1/31/2017 4:07:03 PM 3820 (0x0EEC) Finished remapping variables. InstallSoftware 1/31/2017 4:07:03 PM 3820 (0x0EEC) ZTIGather processing completed successfully. InstallSoftware 1/31/2017 4:07:03 PM 3820 (0x0EEC) Command line cscript.exe "C:\_SMSTaskSequence\WDPackage\Scripts\ZTIGather.wsf" returned 0 InstallSoftware 1/31/2017 4:07:03 PM 3820 (0x0EEC) ReleaseSource() for D:\SMS\PKG\MPS00131. InstallSoftware 1/31/2017 4:07:03 PM 3820 (0x0EEC) The user tries to release a source directory D:\SMS\PKG\MPS00131 that is either already released or we have not connected to it. InstallSoftware 1/31/2017 4:07:03 PM 3820 (0x0EEC) Process completed with exit code 0 TSManager 1/31/2017 4:07:03 PM 2828 (0x0B0C) !--------------------------------------------------------------------------------------------! TSManager 1/31/2017 4:07:03 PM 2828 (0x0B0C) Successfully completed the action (Gather) with the exit win32 code 0 TSManager 1/31/2017 4:07:03 PM 2828 (0x0B0C) Do not send status message in full media case TSManager 1/31/2017 4:07:03 PM 2828 (0x0B0C) Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 1/31/2017 4:07:03 PM 2828 (0x0B0C) Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 1/31/2017 4:07:03 PM 2828 (0x0B0C) Clear local default environment TSManager 1/31/2017 4:07:03 PM 2828 (0x0B0C) Updated security on object C:\_SMSTaskSequence. TSManager 1/31/2017 4:07:03 PM 2828 (0x0B0C) I know this is something i'm missing, something very logical I should get about the placement but alas I do not. Can anyone help me on how I can get this last step going? TIA!
  5. Hello, I'm having a problem enabling BitLocker on Windows 10 v1607 during the task sequence for one model laptop: Dell Latitude E5450 -- except that it does work about 10% of the time. I haven't been able to narrow it down to a specific hardware problem and different BIOS update versions and drivers also result in mixed successes (even on the same exactly laptop). Strangely, the E5450 model has worked historically with the Windows 10 LTSB 2015 version and BitLocker. Models in our environment that work 100% off the time (with the same exactly task sequence) include Latitude E6430, E5440, and E5470. We're using SCCM Current Branch and PXE boot for OS deployment. We do not have any integration with MDT or MBAM. With the E5450s, when it fails it does so at the default Enable BitLocker step. The Enable BitLocker step is configured for TPM Only, create recovery key in Active Directory, and Wait for BitLocker to complete. Also, prior to being built, the computers will have the TPM manually cleared in the BIOS (if previously BitLockered) and the disks formatted at the beginning of the build. Here's a snippet from the smsts logs for the Enable BitLocker step on a failed build: Command line: "OSDBitLocker.exe" /enable /wait:True /mode:TPM /pwd:AD Initialized COM Command line for extension .exe is "%1" %* Set command line: "OSDBitLocker.exe" /enable /wait:True /mode:TPM /pwd:AD Target volume not specified, using current OS volume Current OS volume is 'C:' Succeeded loading resource DLL 'C:\WINDOWS\CCM\1033\TSRES.DLL' Protection is OFF Volume is fully decrypted Tpm is enabled Tpm is activated Tpm is owned Tpm ownership is allowed Tpm has compatible SRK Tpm has EK pair Initial TPM state: 63 TPM is already owned. Creating recovery password and escrowing to Active Directory Set FVE group policy registry keys to escrow recovery password Set FVE group policy registry key in Windows 7 Set FVE OSV group policy registry keys to escrow recovery password Using random recovery password Protecting key with TPM only uStatus == 0, HRESULT=8028005a (e:\qfe\nts\sms\framework\tscore\encryptablevolume.cpp,1304) 'ProtectKeyWithTPM' failed (2150105178) hrProtectors, HRESULT=8028005a (e:\nts_sccm_release\sms\client\osdeployment\bitlocker\bitlocker.cpp,1252) Failed to enable key protectors (0x8028005A) CreateKeyProtectors( keyMode, pszStartupKeyVolume ), HRESULT=8028005a (e:\nts_sccm_release\sms\client\osdeployment\bitlocker\bitlocker.cpp,1322) ConfigureKeyProtection( keyMode, pwdMode, pszStartupKeyVolume ), HRESULT=8028005a (e:\nts_sccm_release\sms\client\osdeployment\bitlocker\bitlocker.cpp,1517) pBitLocker->Enable( argInfo.keyMode, argInfo.passwordMode, argInfo.sStartupKeyVolume, argInfo.bWait ), HRESULT=8028005a (e:\nts_sccm_release\sms\client\osdeployment\bitlocker\main.cpp,382) Process completed with exit code 2150105178 Failed to run the action: Enable BitLocker. The context blob is invalid. (Error: 8028005A; Source: Windows) On successful builds, the snippet is the exact same up to the "Protecting key with TPM only" line. At that point, it continues with the following before moving on to the next step: Protecting key with TPM only Encrypting volume 'C:' Reset FVE group policy registery key Reset FVE group policy registry key in Windows 7 Reset FVE OSV group policy registery key I'm mostly wondering if anyone has seen the errors "Failed to enable key protectors (0x8028005A)" or "The context blob is invalid. (Error: 8028005A; Source: Windows)" -- or has any idea of what could cause this issue. Thank for you any help you can provide!
  6. Hi everyone We are having a weird issue, which I cannot see the reason why! - I have a Windows 10 Servicing Plan setup for CB deployment to a collection. The plan worked a few months ago when I put one machine into it (if i remember rightly)... However we have just started to look into it a bit more and we're coming back with something odd. We add a machine into the collection, it is picked up by SCCM and shows in the deployment monitoring, but they show as compliant! - One machine is on 1511 and the other is on a very very old release, perhaps the first ever release to public. I have trawled the forums and checked the prereq and post install tasks for previous SCCM updates, they look like they're all done. I found a couple of other forum posts with the same issue, but none which have a fix which works for us... Any help would be much appreciated John
  7. Good morning, I have been working on getting an offline OSD task sequence working for some Lenovo Yoga 12 tablets we just purchased, and I do not want to go the route of doing them via ethernet dongle. I've got it to where it will go through the entire task sequence, but something weird is happening that I'm sure will be obvious to someone out there that can help. It goes through the entire task sequence, and when it gets to the end it has added the wireless profile and is connected, but the following has failed: 1) For some reason the local administrator account has a blank password, AND is disabled. The task sequence is set to set our specific administrator password. Not sure why this fails? 2) The last step before a restart is to join the domain, which fails for some reason. When it finishes the task sequence, it does not show any errors. It shows up at the login screen, which no logins will work. It does show that it's connected to our wifi at the bottom, which has connectivity to our domain controllers. Here's a pic of our task sequence order: Do i have something out of order, or just done completely wrong? Any input is greatly appreciated, thank you!
  8. I just recently updated our production SCCM environment to SCCM 2012 R2 SP1, CU1. I updated MDT 2013 to Update 1 (8298) and installed the integration on my central site server. I am now having issues deploying Windows 10 to a VMware VM. After it applies drivers and boots into the operating system for the first time, I receive a pop-up message with the following: "Windows could not finish configuring the system. To attempt to resume configuration, restart the computer". Restarting the computer just brings back the same message. This is only happening with MDT integrated task sequences. I created a task sequence without MDT integration and the deployment finishes fine. I created another MDT task sequence for SCCM and it is still failing at the same point. Unfortunately, I cannot get to a CMD line when the error pops up. I try SHIFT+F10 but that doesn't work. I enabled F8 for the boot image but it is past the PE environment. I did get the logs before the OS restart and they all look fine. I updated our lab environment back in August (pre MDT 2013 Update 1 re-release) and didn't run into this issue. Any help would be greatly appreciated.
  9. I've built a task sequence to build and capture our reference image; windows 10. I have been successful in the build and capture task sequence. I have a couple of application installations built into the task sequence; MS Office 2016 and Chrome. So far so good. The big issue I see with the process is that there is no suspend task. I was hoping for a suspend task, so I could configure the default profile and maybe be able to use copyprofile with the sysprep task. I need to be able to set up a default profile and leverage copy profile in the build and capture task sequences. Does anyone know how to accomplish this or have recommendations on configuring a default profile in the build and capture task sequence? Thanks, Shine
  10. Hi, We are currently running SCCM 1606, and have a mix of Win7 and Win10 images. The probleme is the updated WIM file is not being updated on the DP, there is no error message, it shows up updated time stamp, however the image is not updated and keeps the same size. I'm thinking to delete the current image from the DP then distributing the new one Have you ever seen that before?
  11. 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
  12. Hello, I'm wondering if there is a way to update the Windows 10 applications (downloaded from the Windows Store for Business) via SCCM ,to we can manage and distribute the updates like any regular software. Thanks,
  13. Hi Has anyone had any success in deploying Windows 10 Update 1607 to a Windows 10 machine with 1511 and encryption enabled (in our environment we run Check Point Full Disk Encryption). After the update "installs", the machine boots up and before even showing the Windows splash page, it gets a blue screen with the error 0xc000000f which indicates boot selection failed. The only information i can find from Check Point with regards to Windows 10 updates is from the webpage regarding In-Place updates https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk106433&partition=General&product=FDE Please advise Thanks
  14. Hi guys Hopefully you can point me in the right direction with this one... Please note this is not a question about Driver Packages that would normally be deployed as part of an OSD Task Sequence. Scenario: We are using SCCM (1511) to deploy a Windows 10 OS upgrade to existing Windows 7 clients. The upgrade all works ok and I can deploy the cumulative update from SCCM during the upgrade. I also appreciate I could patch the WIM with this cumulative update (when I upgrade to 1602), but that's a job for another day. I have a number of Dell and Lenovo laptops. Invariably there are a couple of drivers that need to be installed post upgrade. When I connect to Windows Update on the internet, the drivers are downloaded and installed without issue. What I am trying to do is download them from the 'net into SCCM so that 30,000 clients Don't need to go to to the internet for driver updates and... Are ready to go straight after the upgrade. I have configured the software update point component to download the metadata for all classifications and all products. I have configured an automatic deployment rule like this: Properties / Software Updates / Product / Search Criteria / Windows 10 and later Drivers. When I do a preview, there are no driver updates to display. My questions are: Is it possible to download the drivers that Windows Update finds and subsequently host and deploy them from SCCM? If so, am I doing it correctly? If not, how can this be dome without having all clients go to Windows Update for the driver updates? Thanks, Phil
  15. Hello, I am an SCCM new comer, but a long time reader of topics on this blog. This is my first post here. I have recently been appointed to take care of our new SCCM 2012 SP1 environment. I have a task sequence I am using to deploy Windows 10 LTSB with BitLocker to all laptops and mobile devices that pass through our department for imaging. I am experiencing something strange. I am noticing that around 98% of computers that receive the BitLocker enabled image do not "enable" BitLocker on an initial imaging of the computer. What is strange is that BitLocker DOES get enabled successfully once the computer is imaged a second time. I think what is confusing me the most is the fact that rarely the computer will get imaged with BitLocker enabled the first time running the task sequence, and this is inconsistent behavior. I am attaching screenshots of my task sequence steps for BitLocker, but I am unsure of what log to attach if any, and also where to find it. Sorry I'm still quite new to everything. Thank you in advance for any clues or help you can provide. Please let me know what else I can provide to help you guide me. Wardo
  16. Hi! We are going to deploy Windows 10. I'm looking for a way to set the company log as a op-start background (before you log on) But a don't believe is possible with the latest build. is that true ?
  17. Hi All, We are currently setup with the following: SCCM 1606 and are in the process of developing our Windows 10 v1607 SOE and have currently run into an OSD Driver Install issue. We have packaged Dell CAB drivers for E7240, 9020 M/SFF/AIO and added them to an OSD task sequence. The task sequence completes the build, however we find that drivers are not installing. The SMSTS log shows the following errors (Please see screen dump) Our Windows 7 and Windows 8 OSD task sequences have been setup in the same way and we don't have any of these issues, it appears that it only affects Win 10 OSD deployments. Any thoughts?
  18. Hi, We have deployed laptops with Windows 10 build 1511 for a couple of months now. What is the easiest way to upgrade these laptops to the anniversary update (build 1607)? We have SCCM 2012 R2 SP1 Thank you
  19. Yes I know we are WAY behind and need to upgrade, but I do have a question that we can hopefully get around while we work through our upgrade process. We are currently running Config Manager 2012 RCM v 5.00.7711.0000 and upgraded a Windows 7 pc to Windows 10. After doing so, I am getting many, what look look like temp, folders under the root of C:\. It looks to be adding about 20 folders each minute, and in the folder is another folder named Sandbox. I am able to delete them but they just come back. Any idea what this is and can I get around this?
  20. Hello all, We’ve recently implemented SCCM (Current Branch) within our organisation. I’ve previously used SCCM 2003, but obviously some things have changed significantly! We’re having a similar issue to this post: https://www.windows-noob.com/forums/topic/12803-windows-10-enterprise-computer-name-problems-sccm-2012-r2-sp1/ When we deploy our Windows 10 image (1511 Education), we prompt for a computer name (stored in the OSDComputerName variable), however when the OSD TS completes, the machine is named WIN-XXXXXXXXX. I’ve examine the smsts.log file and can see the correct computer name listed within it and it applying to the unattend.xml file [updated C:\WINDOWS\panther\unattend\unattend.xml with OSDComputerName=13-0908-QGT204 (value was 13-0908-QGT204)]. We use the unattend.xml file to apply UK setting (language, keyboard, etc.) to our build. I then removed the “Use an unattended or Sysprep answer file for a custom installation” option from the “Apply Operating System Image” and redeployed the image again. This time the task sequence worked correctly and gave the computer the correct name. Within the xml file I can see <ComputerName></ComputerName> under the “component name="Microsoft-Windows-Shell-Setup"” section, which, I assume, is where the task sequence would update the name – in fact there are two entries, one for x86 and one for amd64 (we only use 64bit) – would this be the issue? Any thoughts or advice is welcome J Thanks, Jono
  21. is there a way to actually know what constitutes as "data usage"? i have an app called Desktopinfo http://www.glenn.delahoy.com/software/ , that simply is just to report local device info on the desktop, and it sometimes will show a large amount of data within "data usage", sometimes from 1-3GB within <=30day period. thank you
  22. Hello, I'm still fairly new to enterprise image building and have only worked with custom Windows 10 images, nothing prior. That said, I had flawless Windows 10 images being PXE deployed up until Microsoft released the 1152 upgrade. After the 1152 upgrade my Window 10 deployment to a new computer went from 20-40 minutes up to 2-4 hours. The process hangs on the "Getting ready" and "Finalizing your settings" screens. Here is my smsts.log file link: http://s000.tinyupload.com/index.php?file_id=70776187637788550876 *You can see in the log the process hanging at 12:56pm and resuming at 2:50pm. OSDSetupHook.exe is where this process ALWAYS hangs. Tools I utilize to deploy images: Microsoft Deployment Toolkit (MDT 2013 Update 2), Microsoft Assessment and Deployment Kit, System Center Configuration Manager (SCCM 2012 R2 Version 1602) (5.0.8355.1306), Hyper-V Manager The steps I take to deploy images: 1. Download Windows 10 1152.2 from MS Volume Licensing website 2. Add Operating System into MDT and create new Standard Client Task Sequence 3. Add cscript.exe %SCRIPTROOT%\LTISuspend.wsf prior to the Imaging section of my MDT task sequence 4. Update DepolymentShare 5. Use the LiteTouchPE_x64.iso to boot a new Hyper-V and wait for the task sequence to hit the Suspend command. 6. While the image is suspended I manually add all the applications our company uses, disable telemtry, powershell script to rip out bloatware, install Office365ProPlus Click-to-run, create LayoutModification.xml for a custom start menu. 7. I will then create a Checkpoint named "Image prior to Sysprep" so I can revert to make changes or install updates. 8. Click the Resume Task Sequence to capture the .wim file 9. Upload the captured .wim into SCCM and tie it into a task sequence that formats and partitions the hard drive, pre-provisions BitLocker, applys the custom .wim operating system, applys the serial number, installs device specific drivers, joins the domain, installs Configuration Manager Client, installs MBAM 2.5 SP1 client, installs updates, applys group policy, and enables BitLocker The issue is that during the SCCM task sequence, prior to installing the Configuration Manager Client, the process hangs on the "Getting ready" and "Finalizing your settings" screens. It will stay on here for 2-4 hours until the task sequence bar returns and finishes the last 4 steps. I've tried countless tips, tricks, different installation methods, etc trying to get the image back down to a reasonable install time. I have even deployed an image with no configuration changes or additional software installed, a default Windows 10 image, and it still takes hours to deploy. If anyone has some insight or has a better deployment method, I would love to get the communities opinion. I have attached screenshots of the MDT and SCCM task sequences. I can also post anything else you guys request. Thanks!
  23. Hello Everyone, I am having a problem when trying to re-deploy an OSD task sequence to machines that have already been imaged. The machines are Dell tablets and we are reusing the same NIC dongles to image them via UEFI PXE booting. I have followed the steps from this article in order to reuse the same dongles: https://blogs.technet.microsoft.com/configurationmgr/2015/08/27/reusing-the-same-nic-for-multiple-pxe-initiated-deployments-in-system-center-configuration-manger-osd/ Our OSD task sequence is deployed to the following collections: "All Unknown Computers", "All Systems", and "All Desktop Clients". Deployment settings are made available to "Only media and PXE" and Rerun behavior is set to "Always rerun program". It seem that when the technician takes a new tablet out of the box since it is seen as an unknown device in CM, it gets the available TS and they can image it. The problem occurs when they try to reimage the same machine, SCCM now sees it as a known device. However, whether the device is known or unknown shouldn't it be able to see the task sequence since I have it deployed to the collections mentioned above? Here is a snippet from my SMSPXE.log: Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16793987" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> 00:50:B6:17:6D:AA, 4C4C4544-0032-4D10-8052-B9C04F474332: device is in the database. Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16793987" ServerName=""><Machine><ClientID>GUID:62efbe3a-9224-4a5a-a2c5-63d6fb7b1190</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM12000F" OfferIDTime="6/17/2016 10:46:00 AM" PkgID="CM100009" PackageVersion="" PackagePath="http://XX-XXX-XX.XX.XX/SMS_DP_SMSPKG$/CM100005"BootImageID="CM100005" Mandatory="0"/></ClientIDReply> 00:50:B6:17:6D:AA, 4C4C4544-0032-4D10-8052-B9C04F474332: found optional advertisement CM12000F Looking for bootImage CM100005 Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16793987" ServerName=""><Machine><ClientID>GUID:62efbe3a-9224-4a5a-a2c5-63d6fb7b1190</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM12000F" OfferIDTime="6/17/2016 10:46:00 AM" PkgID="CM100009" PackageVersion="" PackagePath="http://XX-XXX-XX.XX.XX/SMS_DP_SMSPKG$/CM100005"BootImageID="CM100005" Mandatory="0"/></ClientIDReply> I noticed that when the machine is unknown the SMSPXE.log looks like this: Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> 00:50:B6:17:6D:7E, 4C4C4544-004D-3610-8052-CAC04F474332: device is not in the database. Getting boot action for unknown machine: item key: 2046820353 Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>e2b9e21e-4a0f-40d6-94eb-6ebf20a22d59</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM12000F" OfferIDTime="6/17/2016 10:46:00 AM" PkgID="CM100009" PackageVersion="" PackagePath="http://XX-XXX-XX.XX.XX/SMS_DP_SMSPKG$/CM100005"BootImageID="CM100005" Mandatory="0"/></ClientIDReply> 00:50:B6:17:6D:7E, 4C4C4544-004D-3610-8052-CAC04F474332: found optional advertisement CM12000F Looking for bootImage CM100005 Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> 00:50:B6:17:6D:75, 4C4C4544-0053-4710-8052-B8C04F474332: device is not in the database. Getting boot action for unknown machine: item key: 2046820353 Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>e2b9e21e-4a0f-40d6-94eb-6ebf20a22d59</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM12000F" OfferIDTime="6/17/2016 10:46:00 AM" PkgID="CM100009" PackageVersion="" PackagePath="http://XX-XXX-XX.XX.XX/SMS_DP_SMSPKG$/CM100005"BootImageID="CM100005" Mandatory="0"/></ClientIDReply> Any ideas why it wont see the task sequence? Thanks! Joe
  24. Hello, My company has decided to create and deploy the LTSB version of Windows 10 Enterprise instead of the CB version. Within the build process, we want to have applications populate the taskbar but every time we create the OS build and capture the OS and then test the deployment, the taskbar appears to empty which means that users will need to be instructed on finding the Internet Explorer icon, Windows Explorer Icon and have to drop the MS Office icons there. I might be missing something within the build process so I'm hoping there is a simple solution to creating a more customized desktop environment for users right from the image that gets put on their PCs.
  25. Hi Guys, I try to installl windows 10 (1511) with SCCM 2012 R2 SP1 with MDT2013 Update 2 over PXE. My problem is only one model (Zotak ZBOX ID83 Plus). All other PC'S (DELL, HP, Lenovo) work well. The TaskSequence Aborts by the step "Install Operating System". Network is all the time available The HDD is writable what i tried: - Import the Sata and Netword Drivers in the Boot Image - Bios Update - Format the HDD before OSD - Zero Touch installation (excluding MDT) - The SMSTsLog has no errors. The only way i found to install these Boxes, with an Standalone USB STICK and the ZeroTouch Task sequence. Thanks BoB
×
×
  • Create New...