I have noticed that when you distribute a package to a DP it shows up fairly quickly in the console as 100% "successful" (green). If I then start the execution of a task sequence it will fail due to a package that's not available on the DP..
If I go back to the console, after a while the package status turns over to "in progress" (yellow) instead and won't turn back to "successful" (green) again for 5-10 min..
Cannot find anything obvous in the logs about SCCM resending the package..
Hope this is a RC bug..
3/1/12
MININT- as computername second time computer installs
Experienced an odd behavour when using a boot.iso with unknown computer support enabled.
If I added a computer to the SCCM console and installed the computer, the computer got the same name as I gave it when importing the computer (correct).
But when I reinstalled the same computer a second time it was named with a MININT- name instead..
Created a new boot.iso without unknown computer support (not using it anyway) and the problem went away. The computer now gets the name entered in the SCCM console every time.
If I added a computer to the SCCM console and installed the computer, the computer got the same name as I gave it when importing the computer (correct).
But when I reinstalled the same computer a second time it was named with a MININT- name instead..
Created a new boot.iso without unknown computer support (not using it anyway) and the problem went away. The computer now gets the name entered in the SCCM console every time.
Application with dependencies during Task Secuence
Configuration Manager 2012 (RC2) can handle installation of applications with dependencies during Task sequence execution. (Not possible with Configuration Manager 2007)
Subscribe to:
Posts (Atom)