1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01 Transitional//EN">
5 >Creating Group Prolicy Files
</TITLE
8 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.7"><LINK
10 TITLE=
"SAMBA Project Documentation"
11 HREF=
"samba-howto-collection.html"><LINK
13 TITLE=
"Optional configuration"
14 HREF=
"optional.html"><LINK
16 TITLE=
"Samba performance issues"
17 HREF=
"speed.html"><LINK
19 TITLE=
"Securing Samba"
20 HREF=
"securing-samba.html"></HEAD
31 SUMMARY=
"Header navigation table"
40 >SAMBA Project Documentation
</TH
62 HREF=
"securing-samba.html"
77 >Chapter
21. Creating Group Prolicy Files
</H1
87 >You need the Win98 Group Policy Editor to
88 set Group Profiles up under Windows '
9x. It can be found on the Original
89 full product Win98 installation CD under
92 >tools/reskit/netadmin/poledit
</TT
94 using the Add/Remove Programs facility and then click on the 'Have Disk'
97 >Use the Group Policy Editor to create a policy file that specifies the
98 location of user profiles and/or the
<TT
102 stuff. You then save these settings in a file called
106 > that needs to be placed in
107 the root of the [NETLOGON] share. If your Win98 is configured to log onto
108 the Samba Domain, it will automatically read this file and update the
109 Win9x/Me registry of the machine that is logging on.
</P
111 >All of this is covered in the Win98 Resource Kit documentation.
</P
113 >If you do not do it this way, then every so often Win9x/Me will check the
114 integrity of the registry and will restore it's settings from the back-up
115 copy of the registry it stores on each Win9x/Me machine. Hence, you will
116 occasionally notice things changing back to the original settings.
</P
118 >The following all refers to Windows NT/
200x profile migration - not to policies.
119 We need a separate section on policies (NTConfig.Pol) for NT4/
200x.
</P
127 >21.2. Windows NT
4</A
130 >Unfortunately, the Resource Kit info is Win NT4 or
200x specific.
</P
132 >Here is a quick guide:
</P
138 >On your NT4 Domain Controller, right click on 'My Computer', then
139 select the tab labelled 'User Profiles'.
</P
143 >Select a user profile you want to migrate and click on it.
</P
158 SRC=
"/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
165 >I am using the term
"migrate" lossely. You can copy a profile to
166 create a group profile. You can give the user 'Everyone' rights to the
167 profile you copy this to. That is what you need to do, since your samba
168 domain is not a member of a trust relationship with your NT4 PDC.
</P
176 >Click the 'Copy To' button.
</P
180 >In the box labelled 'Copy Profile to' add your new path, eg:
188 >Click on the button labelled 'Change' in the
"Permitted to use" box.
</P
192 >Click on the group 'Everyone' and then click OK. This closes the
201 >Follow the above for every profile you need to migrate.
</P
208 >21.2.1. Side bar Notes
</A
211 >You should obtain the SID of your NT4 domain. You can use smbpasswd to do
212 this. Read the man page.
</P
214 >With Samba-
3.0.0 alpha code you can import all you NT4 domain accounts
215 using the net samsync method. This way you can retain your profile
216 settings as well as all your users.
</P
224 >21.2.2. Mandatory profiles
</A
227 >The above method can be used to create mandatory profiles also. To convert
228 a group profile into a mandatory profile simply locate the NTUser.DAT file
229 in the copied profile and rename it to NTUser.MAN.
</P
237 >21.2.3. moveuser.exe
</A
240 >The W2K professional resource kit has moveuser.exe. moveuser.exe changes
241 the security of a profile from one user to another. This allows the account
242 domain to change, and/or the user name to change.
</P
253 >You can identify the SID by using GetSID.exe from the Windows NT Server
4.0
256 >Windows NT
4.0 stores the local profile information in the registry under
258 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
</P
260 >Under the ProfileList key, there will be subkeys named with the SIDs of the
261 users who have logged on to this computer. (To find the profile information
262 for the user whose locally cached profile you want to move, find the SID for
263 the user with the GetSID.exe utility.) Inside of the appropriate user's
264 subkey, you will see a string value named ProfileImagePath.
</P
273 >21.3. Windows
2000/XP
</A
276 >You must first convert the profile from a local profile to a domain
277 profile on the MS Windows workstation as follows:
</P
283 >Log on as the LOCAL workstation administrator.
</P
287 >Right click on the 'My Computer' Icon, select 'Properties'
</P
291 >Click on the 'User Profiles' tab
</P
295 >Select the profile you wish to convert (click on it once)
</P
299 >Click on the button 'Copy To'
</P
303 >In the
"Permitted to use" box, click on the 'Change' button.
</P
307 >Click on the 'Look in
" area that lists the machine name, when you click
308 here it will open up a selection box. Click on the domain to which the
309 profile must be accessible.</P
324 SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif
"
331 >You will need to log on if a logon box opens up. Eg: In the connect
332 as: MIDEARTH\root, password: mypassword.</P
340 >To make the profile capable of being used by anyone select 'Everyone'</P
344 >Click OK. The Selection box will close.</P
348 >Now click on the 'Ok' button to create the profile in the path you
353 >Done. You now have a profile that can be editted using the samba-3.0.0
369 SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif
"
376 >Under NT/2K the use of mandotory profiles forces the use of MS Exchange
377 storage of mail data. That keeps desktop profiles usable.</P
396 SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif
"
407 >This is a security check new to Windows XP (or maybe only
408 Windows XP service pack 1). It can be disabled via a group policy in
409 Active Directory. The policy is:</P
411 >"Computer Configuration\Administrative Templates\System\User
412 Profiles\Do not check for user ownership of Roaming Profile Folders
"</P
414 >...and it should be set to "Enabled
".
415 Does the new version of samba have an Active Directory analogue? If so,
416 then you may be able to set the policy through this.</P
418 >If you cannot set group policies in samba, then you may be able to set
419 the policy locally on each machine. If you want to try this, then do
420 the following (N.B. I don't know for sure that this will work in the
421 same way as a domain group policy):</P
425 >On the XP workstation log in with an Administrator account.</P
429 >Click: "Start
", "Run
"</P
441 >A Microsoft Management Console should appear.</P
445 >Click: File, "Add/Remove Snap-in...
", "Add
"</P
449 >Double-Click: "Group Policy
"</P
453 >Click: "Finish
", "Close
"</P
461 >In the "Console Root
" window:</P
465 >Expand: "Local Computer Policy
", "Computer Configuration
",</P
469 >"Administrative Templates
", "System
", "User Profiles
"</P
473 >Double-Click: "Do not check for user ownership of Roaming Profile
</P
481 >Select: "Enabled
"</P
489 >Close the whole console. You do not need to save the settings (this
490 refers to the console settings rather than the policies you have
509 SUMMARY=
"Footer navigation table"
529 HREF=
"samba-howto-collection.html"
538 HREF=
"securing-samba.html"
548 >Samba performance issues
</TD