Re: DNS configuration

orsobubu <postxng@xxxxxxxxxxx> wrote:
Lanwench, excuse me for reposting the same issue, but my google groups
page didn't show my original post until now!! Thank you for your
precious help,

I'm pwecious!

I will immediately correct my configuration.

About DHCP, considering I prefer to assign static IPs, I understood to
disable the ENTIRE service, so also dns dynamic updates will be gone
without negative effects, correct?

Should work, yes.

About forwarders, my routers acts like SuperGumpy said, so I will keep
using the router address as the only forwarder, but I will also try
the alternative option.

If you have problems, change it, but if it works using the router as a
forwarder, fine. I don't think it's going to be as reliable, myself.

I posted these questions about DNS because I'm trying to solve this
problem:
sometimes when an user makes a logon to the network, his roaming
profile
gets impredictably misconfigured: icons rearrange on desktop, programs
lose palettes and menus
or reconfigure themselves from the beginning or do not start at all;
and so on.
And this behavior does not seem to follow some logical way: it
happens
for some computers and some users, but not for other computers with
same profiles or not for other users on same computers. Following some
answers to my older posts,
I reinstalled SBS from scratch and updated all network cards drivers,
without result. Previous experiences on Winserver 2003 Standard never
gave me these errors. Now I'll try to focus on single errors and
alerts in event viewer.

Re roaming profiles: here's my boilerplate.

----
General tips:

1. Set up a share on the server. For example - d:\profiles, shared as
profiles$ to make it hidden from browsing. Make sure this share is not set
to allow offline files/caching!
2. Make sure the share permissions on profiles$ indicate everyone=full
control. Set the NTFS security to administrators, system, and users=full
control.
3. In the users' ADUC properties, specify \\server\profiles$\%username% in
the profiles field
4. Have each user log into the domain once from their usual workstation
(where their existing profile lives) and log out. The profile is now
roaming.
5. If you want the administrators group to automatically have permissions to
the profiles folders, you'll need to make the appropriate change in group
policy. Look in computer configuration/administrative templates/system/user
profiles - there's an option to add administrators group to the roaming
profiles permissions.

Notes:

* Make sure users understand that they should never log into multiple
computers at the same time when they have roaming profiles (unless you make
the profiles mandatory by renaming ntuser.dat to ntuser.man so they can't
change them). Explain that the
last one out
wins, when it comes to uploading the final, changed copy of the profile.

* Keep your profiles TINY. Redirect My Documents; usually best done to the
user's home directory on the server - either via
group policy (folder redirection) or manually (far less advisable). If you
aren't going to also redirect the desktop using policies, tell users that
they are not to store any files on the desktop or you will beat them with a
stick. Big profile=slow login/logout, and possible profile corruption.

* Note that user profiles are not compatible between different OS versions,
even between W2k/XP. Keep all your computers. Keep your workstations as
identical as possible - meaning, OS version is the same, SP level is the
same, app load is (as much as possible) the same.

* Do not let people store any data locally - all data belongs on the server.

* The User Profile Hive Cleanup Utility should be running on all your
computers. You can download it here:
http://www.microsoft.com/downloads/details.aspx?familyid=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en




.

Relevant Pages

  • Re: ROAMING PROFILES & OFFLINE FILES
    ... What would be the best way of removing the roaming prifiles without ... multiple computers, you can restrict that - or just train them. ... If you mean remove cached profiles, ... Also consider redirecting Desktop & Application Data ...
    (microsoft.public.windows.server.sbs)
  • Re: user settings not being saved
    ... Different computers on the same ... roaming profiles will not be fun and I'd avoid using ... If you aren't going to also redirect the desktop using policies, ...
    (microsoft.public.windows.group_policy)
  • Re: Roaming profile versus Redirected folder
    ... computers that are shared during prep periods by the eight math teachers. ... I find that teachers often have problems with roaming profiles becoming ... it's not a good idea to use Redirection with Home ...
    (microsoft.public.windows.server.active_directory)
  • Re: xp pro only network
    ... Michael wrote: ... > network using these computers which has the ability to use roaming ... You can only use roaming profiles in a domain environment, ... Elephant Boy Computers ...
    (microsoft.public.windowsxp.network_web)
  • Re: Local & SBS profiles
    ... computer's local domain (not SBS) and work they way they currently do. ... And they shouldn't log into the local computer once you configure the domain and join the computers from it. ... I remove local user accounts once I've joined computers to the domain and migrated their profiles (note that this will happen automatically if you use http://server/connectcomputer. ... Outlook will go directly to the ISP's mail server. ...
    (microsoft.public.windows.server.sbs)