Originally Posted by
alttab 
there are potentially a number of issues at play here. as others have mentioned roaming profile size would probably be one. Under windows 2008 with win7 it's easy enough to go with redirected folders and have nothing but local profiles with GPO set to clear local profiles after 30 days? i think. Under windows 2003/xp you'd be looking at something like delprof if you were to go the local profile route or as witch mentioned mandatory profiles, both should be coupled with folder redirection.
The issue you have with your wireless is that it is a shared medium, you don't have 100mbps full duplex for each client to pull down large profiles. Wireless by it's nature almost forces one to redesign, whereas 100mbps+ switched networks allows you to get away with all sorts of stuff. so design to keep things lean.
And even without profiles depending on what's happening during start and post-login you could potentially have a lot of network communication going on and each client contending for shared bandwidth. Often wireless that's designed primarily for coverage has situations where a single AP is used to provide coverage to two rooms.
This isn't ideal if you have clients with thick victorian walls on the other side of an AP with the 'strongest' signal or worse if you have a room which has the physical characteristics that demand an AP in the room but there isn't one!!! Especially if you have non-enterprise AP's on the other side.
A good starting point if fixing the profile issue doesn't improve end user experience would be to get to the bottom of how your managed wireless works and optimises as far as it's control characteristics. Another starting would be to look at the type of wireless NICs you have in your end user devices and how they can be optimised [difficult if you've got cheap as chips NICs that don't take advantage of all the cleverness and high specs of modern managed AP's].
ultimately you best is to manage expectations, your client server and network architecture should be architectured as such for a worst case scenario that each user can only be able to obtain single digit MB/s -. Sure in theory your AP can take advantage of multiple radios and on paper provide 450Mb/s and your clients might say they're connected at 140Mb/s or whatever but this is real world where the AP just cannot physically dedicate 100meg to each client during the duration of it's login -many portable devices don't even have the hardware to connect at close to those advertised speeds anyway, unlike what even a decade old Fast ethernet switch and 10/100 network cards can do for instance. The important thing is to try and provide a good experience rather than expect to do on the wireless the same stuff that's done on the wired. Roaming profiles are bad enough on the wired, it can be tear your hair out stuff on wireless.
