Hey,

Great to see you're having fun! I didn't imply you had said imaging, note the separating 
conjunction...

I think I overshot your introducing the Default User point - this is quite valid. 
(Had to re-read original post...) However, you've misunderstood and hence incorrectly 
rejected part of my point yet also state similar. Points I wish to emphasize moving 
forward;

- It is best to fix the problem before it is experienced - at build time
- For those machines already in production, run a script from a Remote Machine
- In both cases - target only the specific objects you wish to customize. (NTUser.dat 
for one. Not the whole Default User Profile)

NumLock before login: (Per Machine)
- Controlled in .Default area of registry
- One setting read for all users of the machine
- Therefore fixed once per machine

NumLock after logon (Per User)
- Initially set inside the Default User Profile's Registry
- Copied from the Default User's Registry and stored in any new user's profile as 
they logon for the first time.
- Saved inside that specific user's profile at logoff
- Read from inside that specific user's profile at future logins

So the "Before Login" and "Default After Login" behaviours are what we might choose 
to address.

(No need to update existing profiles as users can operate the button themselves.)

I maintain then the Best Way to deploy the fix is to employ a Build Script. A Build 
Script is not a non-integral script which runs multiple times as the user logs on 
or starts up, (I'm not a fan of them either) but rather a Build Script executes One 
Time as the machine is dynamically built and does customize the behaviour as you 
will intend for All Future Profiles on every machine. Build scripts are effective 
within organizations leveraging Group Policy as they execute before the policy is 
applied.

The only situation a change might be necessary for machines already in production 
with Existing User Profiles is to address the "Default User - After Login" behaviour 
similar to what you've stated. For these, run the first part of the build script 
to change the default user behaviour specifically by copying a customized NTUser.dat 
to the Default User Profile Directory. (No need to do more.) Such a production script 
can be run from an admin machine reading a text file with all machine names and looping, 
or as a 3 week addition to your company login script. Group Policy could be set in 
a way preventing this, so recommend to temporarily revoke the interfering policy. 
(Foreign ownership could further interfere.) No need to address existing users who 
have likely determined what state they wish to have NumLock in.

Don't get me wrong, a Customized Default User Profile is neat and something I used 
to do, but I wish to convey it may be accomplished with less effort and in a way 
increasingly more ideal the larger the environment gets which I see as "fine tuning" 
the alternative you've generously presented.

Certainly different sized environments will qualify/disqualify certain methods. This 
is quite valid.

Thanks for Sharing Knowledge,
Mike







On Wednesday, March 12, 2008 at 9:09 am, will wrote:

>Oh thats funny.  You read 'fail miserably' and stopped reading.  Large environment 

>has nothing to do with it.  Imaging?  Never said it.....  Logging on to each machine? 

> Not necessary.

>

>My statements still stand:  over 100 users sharing less than 20 pc's=lots of profiles 

>on each.  Can't script a change or use policy here.  Solution: update Default User 

>Profile....only need to once, then copy that one to every machine with a quick batch 

>file.  Imaging?  I wouldn't reimage to fix that, but I *would* update the image 
to 

>include the correct profile...

>

>Having said that, I do agree with the original solution....IF you are able to script 

>something at that site.  A reg file in startup like I also offered up?  Personally 

>not a fan of that.  But if you can't 'script'  due to the limitations I described, 

>then this is a sure-fire method.  An alternative if you will. 

• Reply or follow-up to this message

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum