15:21:10 ! Setup of the branding process failed with E_UNEXPECTED. 15:21:08 ! Setup of the branding process failed with E_UNEXPECTED. The Personalized Settings dialog that so bugged me disappears as quick as it appears. I deploy this as a File Preference by Group Policy and amazingly it worked a treat. inject an install.ins that would cause it to fail, e.g.: So next I tried replacing it with an up to date version as our SOE now has IE9. Delving deeper I found that the branding file was for an older version of IE, Version=8,00,7601,17514. Removing this caused the desktop not to load at all. For me it was in %ProgramFiles(x86)% & %ProgramFiles%\Internet Explorer\SIGNUP\install.ins. One of the suggestions was to remove the install.ins file that holds the branding information. My first thoughts were to strip out the branding. What to do when your SOE has a branded IE embedded in it? The problem is though that in a managed environment using Group Policy for IE configuration, the branded settings seem to fight with the policy applied settings for the final say. The ‘branding’ can include settings like proxy configuration, favorites and security settings etc. Branding is particularly useful in scenarios where Internet Explorer is deployed without the availability of a domain to deliver policy. None of the troubleshooting suggestions helped in this instance, but at least I now had a fair idea that IE (and its branding) was to blame.īranding of IE is done using an IEAK ( MS Link) usually by System Administrators or Application Packagers to package up the browser with pre-configured settings for deployment in a corporate or other environment.
So, what does all this mean?Ī quick big of research on brndlog led me here – and here – EN-US 941158 which were the only links I could find that dealt with delays relating to these logs. 13:39:27 Broadcasting “Windows settings change” to all top level windows…Ī quick bit of maths shows that there’s 53 seconds of ‘broadcasting’ going on for this particular login – even longer in other cases. 13:38:44 Broadcasting “Windows settings change” to all top level windows…
The run of the files seemed pretty normal until the very end: Within these files I found some surprising data….įor each login there were two brndlog files generated, a brndlog.bak and a brndlog.bak. I came across a few log files being written in the Local Application Data (%LOCALAPPDATA%\Local\Microsoft\Internet Explorer), brndlog.* and rsoplog.*.
#Windows rearm count windows#
To kick things off I enabled verbose messaging see (I actual like this level of messaging, even for end users at least you know Windows is doing something when it’s doing its thing).įollowing that came the usual verbose Group Policy logging – Īnalysing these logs didn’t show up any obvious error so I went delving for other logs written at login (system wide) to see it they would shine any light. It was sparked by a persistent message saying Personalized Settings – Setting up personalized settings for: Browser Customizations which was hanging around a bit too long. They can be a University Student, Teaching Staff, TAFE students or even the general public, and each needs a different home drive pointer, different proxy settings (configured for IE and Firefox), and in some cases unique wallpaper and that’s just the start of it.Īs a result, for a number a years I didn’t think too much about login times in the region of 90 – 120 seconds, but earlier this year it became a bit of a bug-bear for me and so the investigations began. Further complexity arrives in the form of different settings required depending on the user type logging in to the PC. Due to SAN space issues we don’t provide roaming profiles, but do redirect Desktops and My Documents as well as a couple of system folders to user home drives. The Environment can be managed to the ‘nth degree but each extra tweak comes at the expense of an extra micro second at login.įor me Management is key as I look after around 3500 student facing and lecture theatre PCs. This is the age-old issue of balancing the need to get log in times as quick as possible v’s keeping the M in MOE.
0 kommentar(er)
