Jump to content


Ariendg

Established Members
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Ariendg

  • Rank
    Member

Recent Profile Visitors

754 profile views
  1. Can you check/show if your system is obsolete and compare ConfigMgr GUID and Previous UUID? Was the newer one approved?
  2. Since I cannot find any discussion about this I decided to start this new topic. Is .NET Framework 4.6 (and 4.7) supported on ConfigMgr site servers? When doing automated upgrades to stay current, the .NET Framework 4.6 will be installed eventually when you're also using Feature Packs Update Classification. Take a look at KB3102467 for example. Reading documentation it looks like .NET Framework 4.5.2 is the only version supported. No "(or later)" to be found here . I think I know the answer to this question, but I want to be 100% certain in my mind it is not supported. Who can co
  3. If updates are working for Windows 7 I would not advise changing settings on the back-end. The base update mechanism is not changed that much from w7 to w10. Also try to find the latest Windows Update Agent download.
  4. Looks like this can be the same problem I experienced with WSUS. https://social.technet.microsoft.com/Forums/en-US/9941646e-648d-49e2-97a4-088e5cc0d917/windows-10-1607-stuck-when-downloading-updates-from-wsus-in-mdt-windows-update-task-sequence?forum=win10itprosetup Don't install (original) build 1607 without CU/Rollups because there are quite some deployment bugs under the hood.. Johan also has blog post about this: http://deploymentresearch.com/Research/Post/540/Building-a-Windows-10-v1607-reference-image-using-MDT-2013-Update-2 I haven't tried the new v1607 media from VLSC, becaus
  5. Can anyone guide me in the right direction for this? This is not a hot topic at the moment I guess
  6. These two errors can be related, depending on your boundary criteria. check out the C:\Windows\debug\NetSetup.log to see why it failed joining the domain. Extra for the application actions: Do you have SMSMP=<fqdn of site server> in the 'Setup Windows and Configuration Manager' task? Example: http://ccmexec.com/2013/09/tips-when-building-images-with-configmgr-2012/ I assume the client where the TS is deploy is a VM? Otherwise check similar app errors: https://www.windows-noob.com/forums/topic/10746-error-0x87d00269-when-installing-application/ Selected the Current Branch default o
  7. I can't seem to find the right information about network limitations during Operating System Deployment with ConfigMgr. Is this possible? Where can I find info about this? I believe 'client settings' are not active when the OSD Task Sequence is still in provisioning mode. correct? I have found this topic on the windows-noob forum: https://www.windows-noob.com/forums/topic/7780-osd-throttle-bandwidth/ (no replies unfortunately) And something on uservoice: https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/15043629-bandwidth-throttling-for-osd Can I conclu
  8. I would like some more background information for the auto upgrade about https://technet.microsoft.com/en-us/library/gg699356.aspx from my fellow ConfigMgr noobs Situation: I have all my customer clients running ccmclient version 5.00.7804.1000 (ConfigMgr 2012 SP1 without having a site server) and want to choose the best solution bringing all clients up to date (to ConfiMgr 1606). SCCM (CB) is being implemented and all clients will connect/report to the site using AD discovery. My first tests provide me with the situation only a forceinstall or an uninstall+install give a working
  9. Exit Code 16389 is a code you only will see at application deployment. Changing back to packages will be our last resolution because of a few advantages. Why is using application deployment after OSD no problem I cannot understand. In my opinion it is not that different. Provisioning mode true and ServiceUI But back to topic please.
  10. Same strange random problems with installing applications In OSD/Task Sequence with ConfigMgr R2 2012 (Cu3) here also. The task sequence failed to install application <APP> for action <ACTION> in the group () with exit code 16389. The operating system reported error 2147500037: Unspecified error The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of 16389 was returned. No appenforce.log created! smsts.log errors: NotifyProgress received: 24 (Application download failed ) Execution status received: 24 (Application
  11. Solved for us. In our case the problem was caused using the F11 key (for fast PXE boot) instead of the F12 (boot selection menu). Very strange behavior with the newest generation Fujitsu hardware or is this 'working as designed' and also an issue with other vendors? Addition: VM was working and Task Sequence Media (ISO) using F12 again was also working.
  12. These are the things we're already doing with the non-powershell equivalents commands. Diskpart can also initialize the disk.
  13. Unfortunately this is not helping for us. We're doing manual diskpart select disk 0 -> Clean and Format for every deployment in the Initialization phase.
×
×
  • Create New...