Displaying 20 results from an estimated 50000 matches similar to: "Problems when migrating from an old machine to a new one."
2006 Feb 27
2
NTUSER.DAT, user's settings
Hallo!
I have reinstalled the server, specially the Samba PDC.
I copied all the data back and the system seemed to work. People were
able to log on and had the drives mapped.
Now, at the day "0" after reinstall, the users cannot work. The user's
settings on the "Windows 2k Professional" machines are not adopted. They
all have their desktops and own documents, but the
2005 Aug 18
1
how to use cmd profiles
Hi
I have a problem with the cmd : profiles.
I want to change the sid in a ntuser.dat.
I have already read many message in mailing list who explain how to use
profiles
but it's dont't work.
i use profile like this:
profiles -c S-1-5-21-my-old-sid -n S-1-5-21-my-new-sid ./ntuser.dat
on the output i see the new sid like i want but the change take no effect on
the file
when i do
2005 Mar 04
1
'profiles' command with WinXP Profiles
Hi all,
I have gotten the 'profiles' command to work for NT and Win2K profiles very
well. In Windows XP, I am able to change the 'owner' but not the 'group'
SID. It gives no errors but it just doesn't change them. A snippet of the
profile in question is below:
furnsrv:/data/samba/profiles/jon # profiles NTUSER.DAT |grep S-1-5
Owner SID: S-1-5-32-544
Group
2008 Jan 04
2
Roaming profiles and case sensitivity
Hi,
Yesterday I found big problems concerning my roaming profiles. They seem
to work on some computers where they are always used, on some other the
did not load properly (i.e. a default profile was loaded instead).
After some debugging with userenv.log I found the very strange problem:
case sensitivity for ntuser.dat!:
[...]
IsCentralProfileReachable: Testing <F:\testuser\ntuser.dat>
2011 Mar 06
2
Mandatory User Profile
Hi,
first of all: my name is uli... i'm from bavaria/germany and i'm working
with linux quite a long time (maybe 10 years).
Now my "problem":
my samba is setup with ldap-backend. my configuration with mandatory
profiles is working quite good. i created a Default User - Profile in my
netlogon-share (migrated from a windows-xp client). ntuser.dat has been
renamed to ntuser.man.
2005 Nov 30
4
migrate profile from an old server to a new one - SID and ntuser.dat problem
Hi,
my problem is the following:
i am trying to replace an old SUSE 8.2, Samba 2.2
domain controller with a SUSE 9.3 system with samba
3.0 as PDC.
Everything works fine, i can join the new domain, i
replaced the machine and domain sid from the new
server with the old ones.
But how can reuse the profiles from the old machine
at the new one?
If i make a simple remote copy, the settings of the
2005 Jan 21
2
change SID in ntuser.dat
Hi all,
I want to migrate from 2.2.6 to 3.0.10 (with ldap). Is it possible to change
the SID in the ntuser.dat on the server-saved profile?
-Peter
2004 Dec 02
2
mandatory profiles
Hello!
I am running samba 3.0 on fc2 in a win2000 network.
I want to use only mandatory profiles in the network, but can't get this to
work properly. I have set up a "perfect user" on my local machine", and
copied this profile to \\server\netlogon\Default User. I have also made this
default profile mandatory by renaming ntuser.dat to ntuser.man.
In smb.conf I have added:
2007 Feb 06
3
ntuser.dat
What are the implications of locking the ntuser.dat file on the user's
server profile? That is, if I make the ntuser.dat file read-only, what
affects will that have on the client?
2003 Oct 08
1
Can't do roaming profiles
I need a little advice on finishing off a Samba PDC. I have Samba
3.0.0RC1 installed and working as a PDC on a Redhat AS 3.0 machine. It
authenticates users nicely but the "roaming" profiles don't work.
Tailing the samba log, I see the an attempt to access the users
ntuser.dat file, which doesn't exist before the first logon, when
logging in. The profile directory
2003 Jan 15
4
Profile migration again
John H Terpstra jht@samba.org writes:
> You see the NTUser.DAT file is keyed to the user's SID and the Domain SID
> of the NT4 environment in which they were created. You need to either use
> the NT4 procedure as documented in the resource kit for migrating the
> profile, something that Microsoft only supports within the one domain
> anyhow, or else use the profile editting
2010 Apr 07
1
Problem with `profiles`
I'm trying to move some roaming profiles from Domain A to B. All of the
profiles are from XP SP3. The originating machine is Debian 5/AMD64, samba
3.4.5 from Debian packages. The destination machine is Ubuntu 9.10, but x86.
From everything I've read and found online, `profiles` is supposed to work for
XP with no problems. When I attempt to do a SID change on NTUSER.DAT, I get
2007 Apr 01
5
How to change SID in ntuser.dat?
Hello,
i try to migrate user/groups from NT4 PDC to Samba3 with LDAP backend.
There is already an NIS-Server with Samba runing, so there exists two
userlists.
I migrated the user/ groups from windows via net rpc vampire and
added/changed
the UID?s from the NIS-Server but didn?t change the SID.
A teammate told me, there could be some access problems, if i don?t
change the SID.
So i tried to change
2006 Sep 13
1
security with normal profiles
Following TOSHARG and "Samba 3 by examples" I implemented
Folder redirection plus some security restrictions by building
a custom NTUSER.DAT which is the default profile of my users.
The problem is that each user has read/write access to its profile
share therefore he can replace its NTUSER.DAT.
This is why I chose mandatory profiles.
Is there another solution?
The problem with
2006 Sep 02
2
Roaming profiles errors and shares not disconnecting
Hi,
We are using Samba 3.0.22 on FreeBSD 5.5 PDC with ldap backend and
roaming profiles.
We meet some difficulties when users logout from some Windows 2000 SP4
clients, and storing their profiles back to the Samba server.
The file NTUSER.DAT seems to be uploaded and stored in lowercase, as
ntuser.dat.
Then, when users try to reopen a win session, they get a corrupted new
profile. This new
2003 Nov 07
1
Problems with migrating profiles
Not strictly a Samba question but hopefully someone has a solution. We run
samba as a pdc for an office network of 2000/XP machines, the machines is
old and dying, I have installed samba 3 on a new server and given this a
different domain name.
I can join machines to the new domain no problem, I can create new samba users and log in with them on the machines, the
problem is when I try to migrate
2004 Sep 28
3
Roaming Profiles:Samba PDC:WinXP:User must be local admin
I'm having a problem with Roaming profiles in Windows XP with Samba as PDC.
I've googled and trolled the mailing lists and read the Samba documentation.
Problem:
User logs onto domain from WinXP client and profile is downloaded (you can
tell because it takes a long time and lights on hub are lit up). However,
unless that user is in the admin group locally, all/some of the profile
2017 Jan 26
1
[4.3.11-Ubuntu] SMBD keeps Locks on NTUSER.DAT and ntuser.ini after logout
After having migrated my machines and user to Samba 4.3.11 on Ubuntu 16.04.1
(no domain upgrade, new provision, all accounts new defined) and old data
copied over to the new machines, I have now a broader testbed and notice
issues I didn't see prior to that.
Having roaming profiles (defined in the user object in LDB)...
Seemingly at random smbd keeps locks on NTUSER.DAT and ntuser.ini for a
2002 Aug 12
2
PDC roaming profiles and templates
Greetings!
I have configured samba as a PDC.
This works fine so far, I can add users, log in at my Win2k workstations and
use roaming profiles. But now my problem: I want several "template"
profiles. I want to use several different pre-configured base-profiles.
1) I configure a template-user: configure the corresponding Desktop,
network and printer connections and so on.
2) After this
2003 Jan 14
1
Problems with migrating from local to roaming profiles
Hello everyone! I have had a lot of luck with mailing lists in the past, so
I'm hoping this one works out well also. I've recently helped my company move
from an NT4 PDC to a Samba 2.2.7a PDC and everything has gone smoothly until
this point. We made the decision to migrate to roaming profiles so our users
could move around and use whichever computer they wanted to unlike before,