Jump to content


Garistotle

Established Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Garistotle

  • Rank
    Newbie
  1. Hi, Same issue here. Now the Monitoring node is showing this deployment as unresponsive. The app that MDT was stuck on (Symantec Endpoint Protection) appears to be functioning on the deployed client machine. In fact, everything about that client machine seems to be fine, it just looks like it hasn't told MDT that it's finished. I can see several "Failed to save the current environment block" errors, but again, they don't appear to have caused a fatal error. The only posts I could find suggested updating ADK, and ADK is current on this machine. I keep trying to upload my smsts.log but I'm getting "Upload skipped (Error IO)" when I try. If you have any recommendations, I would appreciate them. Thanks!
  2. Hi, thanks. I tried re-deploying the task sequence this morning, no change. I just updated the boot image on the DP and again, no change. The boot error on both my Hyper-V client and a Dell laptop is the same: PXE-E53: No boot filename received On the VM it shows the same error, then shows "Boot failure. Reboot and Select proper Boot device or Insert Boot Media in selected Boot device_ SMSPXE.log shows the above, but continues (error-free) with... PXE::CBootImageInfo:::CBootImageInfo: key= Adding [site]00004.4 Adding [site]00005.5 Adding [site]00019.3 Adding [site]0001A.3 Found new image UCO00004 (goes on error-free) ... To my understanding, this would indicate that the task sequence and boot images are where they're supposed to be. mpcontrol.log is largely error-free with the exception of... CMPControlManager::PublishDNS: DnsReplaceRecordsSet() failed with status 9017. This is a new site that I'm configuring in preparation to migrate clients to when it's all ready to go. I thought I was getting that mpcontrol error from having added the 2 Application Catalog roles, but not having a DNS redirect yet. This seems unrelated to the problem I'm having, but maybe not? Are there any logs that will show me some more detail about what's happening when the client is requesting the boot image? Any other logs I should look at? Thanks for your help! And, all that you do to help us learn config mgr!
  3. Same exact output from SMSPXE.log. Did you ever manage to find a solution? I'm configuring a new 1606 site and haven't yet successfully PXE-booted my build and capture task sequence. I disabled and re-enabled PXE on my DP, but I really don't want to go through all the steps you had to go through only to find that it didn't work. From looking at the other posts about this issue, it looks like that might fix the issue when the site has been upgraded from R2 to CB. If I find something that works for me, I'll post here.
  4. Hi Everyone. First time here, thanks for reading. When I first deployed Office 2013 my org wanted nothing to do with OneDrive, so I removed OneDrive via OCT in "set feature installation states" and in addition, used the "block signing in to Office" setting found in the OCT under Features > Modify user settings > MS Office 2013 > Misc. Now, they want to use OneDrive. To reverse those earlier customizations, I need to make sure I change the right things. Here 's what I think I need to do: 1. Configure the "Org ID Only" setting via OCT in the MSP file used for Office deployments, then update the content on the DP. 2. Configure and enable the same setting via the User GPO found in User Config > Policies > Admin Templates > MS Office 2013/Misc > "Block signing into Office". The intent is that the first change affects new deployments going forward, and the second overrides that change in the MSP when GPO is applied. Is this right? Or, would the change to the MSP apply to existing installations after the content is updated on the DP and clients complete hardware inventory cycles? Do DP content updates to existing installations of software work like that? Or, would I need to send out a whole new deployment?
×
×
  • Create New...