Jump to content

OldSchool76

Member
  • Posts

    3
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About OldSchool76

Profile Information

  • OS
    Windows 7 x64

OldSchool76's Achievements

0

Reputation

  1. I uploaded three new tests (additional executions) 5 - All Services Enabled (Baseline) 6 - AppV and MICMUTE OFF - McAfee On 7 - AppV and MICMUTE ON - McAfee OFF Boot performance still seems to suck. I agree that the Profile section seems odd but have come up with nothing yet. SkyDrive Link: http://cid-e8b5bbf49ba20713.office.live.com/browse.aspx/.Public New Zips with ETL
  2. We have test running with McAfee 8.8 that show a 30% improvement. I will run another pass with it completely removed. The Profile issue is the one that is vexing. The test machine only has one user and it is not a romaing profile. (Will double check, but that is not our default configuration) Furthermore, on 3 test runs on the Test PC, the folowing pattern emerges: WinLogonInit Breakdown Test Pass CreateSession Logon Logon.Profiles Logon.GPClient StartShell 1 104 164309 161111 3191 3 2 75 187395 72991 114395 2 3 176 110287 110246 0 2 I wish there was a batter way to format that for you but the delay moves from PRofiles to GP Client. Test pass 1 is in default config (you have that trace) Test pass 2 is with MICMUTE and SFTLIST Disabled Test Pass 3 is with all Lenovo services disabled (admittedly a shot in the dark) Why would the delay flip flop? No policy changes are happening.
  3. Wow. Looks like this is the place for the help I may need. I am trying to troubleshoot intermittent slow boots with Windows 7. I have run a number of test passes and have logs from bootmgr runs. It seems like I have pain both in MainBootPath (WinlogonInit) and in PostExplorer but I am focused on teh WInLogonInit. Looking at the xperfview it seemed that the AppV client (sftlist) and the Lenovo MICMUTE services were causing the problem. Disabling them in the production machine seemed to improve performance (Link) but in the test machine, the performance still sucks. The machines are running SSD. The other odd thing (to me, maybe not to you guys) is that the time hog in WInLogonInit seems to switch between WInlogonInit.Profiles and WinLogonInit.GP Client. Any thoughts? Traces http://cid-e8b5bbf49ba20713.office.live.com/browse.aspx/.Public?uc=4 Two for the Production Machine (All Services and then with the two suspects disabled) and two for the test machine (which is not reproducting the improvement in behavior) Any.all help is appreciated. If it is helpful: Test Pass PreSMSS SMSSInit WinLognoInit ExplorerInit PostExplorer (Not in MainBootPath) Test Pass CreateSession Logon Logon.Profiles Logon.GPClient StartShell Normal Run 3628 9203 178985 2893 71700 Normal Run 326 160281 156497 3778 6 Run 5 3707 8733 169326 4547 43000 Run 5 168 154490 47184 107283 4 Run 6 3316 9428 173920 5159 55100 Run 6 168 168327 168252 1 2 Run 7 3255 8850 59273 2031 33900 Run 7 83 54272 50930 3336 38
×
×
  • Create New...