Groupe des Utilisateurs Altiris Suisses et Francophones Group

That is really strange: We notice this only some older XP machines, with previous install of ns6 agent, dell client manage and or KACE client previous install.

What I do, when I see the NS7.1 Symantec Management Platform Agent (Aexnsagent, 7.1 sp2), keeping trace older NS6 server NSE outbox message in error. I do remove the agent with the /clean utility option. And reinstall new NS7 agent with reboot the computer.

I still have the same issue:

• After the user log in: The computer is doing "nothing", during about 1mn, to 1mn20 as I see (customer tell was also possible a big longest time).
• We reproduce this "wait" each boot. (I forgot to try a second log in, without reboot, I will ask for)
• We can workaround using a "Ctrl-alt-del" strike, open immediately the normal explorer Windows (doing after 30 seconds, or 15 seconds, that is immediate opening windows menus (explorer).
• Nothing notice on the system logs, We see an Intel AMT registration event log error, but when "deactivating" this service, not solving this issue.
• and no more errors on NS7 agent logs...

1 mn, 1mn20 looks like a TCP session time-out... I should perhaps activate some "Packet sniffing" monitoring.

Does anybody got a similar issue ? I do not see existing similar cases.

For information to Symantec employees :)

Did you try to put a blockout at agent start? Are you experiencing the same behaviour?

I don't have the Dell Client Management and did not experienced this kind of issue (I am using both switch /unintallagents and /clean while uninstalling NS6 agent)

Hope this will help.

Regards,

Cédric DUBIE

Maybe I'm missing something, but this could be a large profile.  Is it just taking a long time to create the user profile?  How big is the Default User profile (C:\Documents and Settings\Default User)?

Is the drive encrypted?  This can increase login times.

As you also said, they're older machines.  Maybe I missed it -- what makes you think it's Altiris in this case?  Nonos' idea of a Blockout during startup/login is a good one.

Thanks Mike , Cedric,

no encryption, no 1st logon new user: user profile already there. I will investigate more this afternoon.