allen2

If users only have modify they shouldn't be able to change permission as you need full control for this. As rights are inherited from parent the new created folders will also get the right rights unless you didn't removed the account "CREATOR OWNER" from the accounts with full control.

Yes.

I would do it this way: Sub confirmation2 Dim A1 A1 = MsgBox("Recovery Complete, Would you like to Restart now?",4) If A1 = 6 Then Set objShell = CreateObject("WScript.Shell") ObjShell.run("cmd /c wpeutil Reboot"),0,True End If End Sub

There are free gui tools like supercopier. Or you could use a cli tool like robocopy.exe.

As far as i know, if you have tcpip.sys from sp2 or later it is 10 and unlimited otherwise.

To my knowledge, there isn't a fix for ide drives using atapi.sys. But this wasn't a problem for most scsi drivers.

When you apply many gpo to same computer and user, you need to activate loopback processing with merging.

High would the value 3. As for the reason, the only thing i see is a gpo.

No custom adm file don't need to be copied on target comp but might be needed on DC or computer when you need to edit this gpo.

I know how to do it manually after install but doesn't know how to do it unattended.

Manually : set view to page, go to first page you want to delete, set view to normal then remove all after the page break until the next page break including it (if you only need to remove one page). Do this for each page you want to delete.

There's enough Process Monitor Registry auditing to keep busy with until the Windows OS no longer uses a Registry. So many of the application issues I've encountered during image development were due to meaningless Registry references to the account used for mastering the Default User profile, that I now use/recommend this approach. I agree that "doing a real job of..." is a worth-while skill to have, though it can be tedious. I use regshot and shot before installing the new application and shot again after install then again after first launch of the application and its customization. Then i use the compare of regshot and i know all modified/added/removed registry entries during the customization and /or install process. Original post has been modified to try to alleviate confusion around what scenario this process is intended for: Image development and profiles whose Registries are not copied between computers (non-roaming, etc.). I apologize. No need to apologize, i understood that point, but my point was that you might not deploy again all client computer when a new application is needed unless you want to work a lot more. Which is to keep a database of applications and their Registry entries, then modify as-need, possibly by using .ADM templates or multiple run-once logon scripts, right? Exactly. By reconfiguring Registry entries you've identified as needing special attention, right? Most of the time, there only a few registry entries for each application. Such as a default templates directory the user might already have chosen? Hopefully that is not overwritten when your solution is applied. How does one know what is all right to overwrite and what is not, when a user has already generated a profile and possibly customized it? Through careful scrutiny? Is that what keeps us employed? Yes for example, but there a lot of other things like mails settings, toolbar position and behaviour etc... Most of the time in this case, i was just asking the user what was missing after giving him the new profile and restore part of his registry and files. And yes it is something that keep some of us employed. Using subst P: "%userprofile%" is a great idea for dealing with REG_SZ. Then your .ADM templates can be used to throw P:\ in such entries. Do these Group Policies enforce these settings permanently? Yes unless you reset them to another value. They are mandatory for applications which need it but it save a lot of work and end users are happier because they don't loose their setting like their childs picture set as wallpaper. I agree : That's the better way to do things.

The 2GB limit is only for the older format and yes since 2003 native outlook 2003 pst files. The corruption might still happen for networked pst files but i never local pst files getting corrupted since using the new file format.

That's what i call a wired connection. If you want to be sure the computer is clean, you'll have to reinstall it but that's a little extreme. The only other is to use tools like autoruns (from sysinternals) to clean manually then disable all unneeded services then use a firewall.

I was just saying that replacing might be very dangerous and mess with default profile hive but that's all. I agree that is very unlikely that this string is found elsewhere right now. I prefer doing a real job of finding what registry changes are needed but that's my way of working. Also as you're planning to deploy this with gpo, you should know two things: - your script will only affect default profile and all existing profiles (on client computers) will need to be recreated to get the new settings. - your script will execute at every reboot or login. That's a lot of work but my solution will affect existing user profile without the need to reconfigure users profiles because if you recreate existing user profiles, you'll loose at least their existing setting unless you backup/restore them after (but that a lot more complex). Also for your reg type and variables, you could easily solve it by doing something like this in the login script: subst P: /d subst P: "%userprofile%" With something like you'll only need to do the job once (the replace stuff) and it'll work for all user.

I would be very cautious and use it in an usb enclosure (to avoid the reboot). Also as the drive report a high temperature, i would use some system to cool the drive even if the temp isn't reported correctly.

Your regreplace script might be very dangerous in some case: you're replacing all values found in user hive so it might replace unwanted values for a some user login. In my experience, setting directly the %userprofile% in default hive is the best solution. Also as you're planning to use gpo to deploy the settings, i would go a different way: I would use regshot to identify the registry entries for each application and create a gpo for each application with custom adm or/and script if needed.

To rename: http://support.microsoft.com/kb/298593 And reg.exe is here for your registry needs.

Probably, you can check it by launching dcomcnfg and expand Component services, expand Computers, expand My Computer and then expand com+ applications, you should see the components using msdtc.

Did you tried this: if not exist "%CDROM%\1.EXE" goto next if exist "%CDROM%\1.EXE" (start "" /wait "%CDROM%\1.EXE") :next "D:\2.EXE"

If you use %userprofile% in the reg entries before deploying this default profile it should work.

Did you checked "Allow connections from computers running any version of Remote Desktop" box on the Windows 7 ?

Did you tried this search engine http://www.filewatcher.com/ ? Just found a firefox addon: fireftp which seems to do this.

Yes, most likely data in the msdtc folder are corrupt so renaming is just to save the data. Or you could just empty the msdtc folder (it's the path of no return). Then do the msdtc -resetlog <= should recreate all needed log files. And after the reboot, the errors should be gone. About the applications using Msdtc, it could be a backup software( like Symantec backupexec system recovery) or IIS.

Or you could have just edit (notepad or another text editor) and search through the default .adm policy (in this case system.adm).