Hmmm...
my experience with it is also sporadic, although I notice that early in the morning, like now, when the network is quiet, the login script runs just fine... but later in the day once everyone gets here and the network gets loaded up, it seems like the AnyConnect delay is more pronounced, and this causes the attempt to fire the \\DOMAIN\netlogon\CompiledKixScript.exe script to "miss" (for lack of a better word).
I can't find anything in Active Directory that would allow me to insert a pause or delay before having a workstation try to run a logon script. Since we also have remote users VPN in first, before actually logging into their remote PCs, not sure the OnConnect script option would be better (the great irony there is that most of the remote machines are Windows XP and on Windows XP, the logon script runs fine no matter what time of day).
This issue only manifests itself on our Windows 7 32 bit machines. May have to get with our infrastructure lead to get an official ticket started with Cisco, since these message boards are slim pickin's as far as any clue on this one is concerned.
