In this article, I will describe in depth how a package and program is created. Why the older package and program process and not the newer application model? The application method may come next, but mostly I wrote this to share the information with a peer and because it is more depth than most articles I see on the subject. I will describe the process from the time the Configmgr admin creates the package in the console up until the time when the newly created package a program(s) are distributed, distribution of a package warrants its own article at this depth. Specifically I will show how the different Configmgr components are involved, what logs are written to, what you should see in the logs, as well as some additional details like the inboxes, files created for processing and additional details that are not typically discussed. If you are new to Configmgr, this is not a good article to start with as I assume there is some basic understanding of Configmgr terminology and its process.
This is the first article in a series of articles on Windows 10 deployment and management. In this first article, I will cover some of the basics for a refresher or if Windows 10 is your first time deploying an OS. I will also cover what has changed or updated recently as well as what is new. This series will get progressively deeper into deployment and then I will cover management of your newly deployed Windows 10 computers and devices starting with the basics again followed by deeper technical articles. With Windows 10 being available on July 29th and the paradigm shift in Windows and Windows deployment my intention is to provide enough information to enable others with the ability to confidently deploy and manage Windows 10 before the 29th of July.
Series of articles:
- What is new in Windows deployment
- Options for deploying Windows 10
- How-to successfully deploy Windows 10
- What is new in Windows systems management
- Options for managing Windows 10
- How-to manage Windows 10