thingy
29-08-2004, 05:08 PM
Got a few weird things happening at work that I don't understand and I would like some help. MCSE books don't quite seem to explain well enough how login scripts work as far as caching it and making changes etc.
First problem is, we run batch files at work for login scripts which are called from Group Policy. This works well most of the time, but if I make a change to the login script it doesn't seem to take much affect until I completely get rid of the GPO & create one (login script too) all with different names. Is there an easier way for enforcing changes in login scripts so machines don't run cached copies? I have no idea where this cache is kept or how this interaction works in detail.
Second, there's a few laptops I've built with a standalone copy of WinXP Pro. They don't seem to like running the login scripts at all. All the machines built by just changing the pre-installed version of windows work fine, but not the ones from my CD. I don't have any idea where to even start looking for resolving this issue.
My own laptop is a sufferer. One thing I found strange was my Active Directory profile never mapped the drives etc from the login script. I bring the laptop home, log in under a different profile, and I see all the drives there (disconnected). :eek:
First problem is, we run batch files at work for login scripts which are called from Group Policy. This works well most of the time, but if I make a change to the login script it doesn't seem to take much affect until I completely get rid of the GPO & create one (login script too) all with different names. Is there an easier way for enforcing changes in login scripts so machines don't run cached copies? I have no idea where this cache is kept or how this interaction works in detail.
Second, there's a few laptops I've built with a standalone copy of WinXP Pro. They don't seem to like running the login scripts at all. All the machines built by just changing the pre-installed version of windows work fine, but not the ones from my CD. I don't have any idea where to even start looking for resolving this issue.
My own laptop is a sufferer. One thing I found strange was my Active Directory profile never mapped the drives etc from the login script. I bring the laptop home, log in under a different profile, and I see all the drives there (disconnected). :eek: