![]() Startup is the period after the user sees the desktop during which all Startup Items start running, including applications that load into your System Tray or the processes you see starting within your Task Manager. The Shell section starts when Explorer.exe is fully running and is complete when the user receives keyboard and mouse control and, lastly, sees the desktop. The third section of the login is the Shell. The last step here is to kick off Explorer.exe. This is where logon scripts are run and network connections are made. The second section of the login is the Userinit. This section is where Group or Local Policies are run, including non-login scripts. The first section of the login is the Pre-userinit. I then have Startup Items as a fourth section of the login process. The login process is formally known as an Interactive Session, of which there are three main sections. The login process to a Windows machine is rather complicated, but I will provide a basic breakdown below. While previous blog entries, specifically UWP applications and Active Setup, could be considered Startup Items, this blog is specific to the Startup Items noted above. While optimizing Startup Items is important to the end user experience, it doesn’t reduce the user logon time, meaning the time between entering user credentials prior to seeing the desktop. The purpose varies, but it could be as simple as starting an application like antivirus or customizing an application that exists for this specific user. ![]() Run and RunOnce registry items are used by application developers to run certain custom items when a user logs onto a computer. Unless otherwise stated, the Run and RunOnce scenarios discussed in this blog focus on items that specifically affect Startup. A breakdown of these scenarios will be discussed later in this blog. In each scenario, these registry values will run differently with different time frames and in different contexts. While the login time frame is easy to identify, the Startup period isn’t easily capturable.Ī quick note: Run and RunOnce registry values exist in user and machine contexts as well as 32-bit and 64-bit operating system contexts. The Startup Items denoted here are special in that they don’t affect a user’s traditional login, which is the time when the user initiates a connection to the machine – whether physically or through a virtual broker – to the point where the user sees a desktop. The biggest area of optimization for Startup Items are Run and RunOnce registry keys, with a few other sections I will explain later. The term Startup denotes the period after a user has control of a desktop but before all Startup Items are finished running. While they have changed over the years in how they are implemented and what can be done with them, each startup item can negatively impact the user experience and result in higher resource utilization than desired.įuture blogs will discuss how to optimize your Windows OS environment through Autologgers and Windows Optional Features. Startup Items for Windows OS have been around since Windows 95. More specifically, we will discuss their purpose, how they work, and what can be done with them for the purposes of optimization. This blog addresses Startup Items, which includes Run and RunOnce Registry Keys, as well as the Startup folder that exists in each user’s profile. In each case, we discussed what each piece is, how it works, and how to optimize it. The third entry covered Services and Scheduled Tasks. The second entry covered the Microsoft® Store. Be sure to vet any optimizations carefully and test the optimizations described in this series internally before pushing the changes to your production environment. Of course, the optimizations provided in this blog series are intended only as a guide. This series aims to share the seemingly infinite number of ways you can optimize a Windows environment, with something for beginners as well as administrators familiar with optimizations but looking to deliver an even better experience within their environment. ![]() Hopefully, these optimizations will be just as good to administrators of physical machines as to a virtual environment utilizing Nutanix Frame®, Citrix® Virtual Apps and Desktops, or VMware Horizon®. ![]() I will attempt to keep these optimizations as environment agnostic as possible. This blog series introduces you to Windows® Operating System (OS) optimizations, starting with version 1903. As with any software, what is provided to you is what the developer intended, but not necessarily what you want or need for your end users. Operating systems can be a lot of work for administrators – work to configure the image, work to install the applications, and work to provide the best user experience possible. Business Continuity & Disaster Recovery.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |