Topic: Help: no roaming profiles using win7

[gjverheij]

Hi,

At the latest moment I change to windows 7. I have used the description at http://wiki.contribs.org/Windows_7_Support to join a SME Server 8.0 Domain with Win7.
The sme-server gave a welkom at the join. I have reboot my windows 7 client and log on again and close it. But I can't find any data in the profiles folders of the sme server.

Do I miss something?  Could you help me with a suggestion?

Gert-Jan

[brianr]

Can confirm I have 2 sites where Win7 Pro is authenticating using domain to SMEServer 8.1, however not using roaming profiles.

[Stefano]

Hi,

At the latest moment I change to windows 7. I have used the description at http://wiki.contribs.org/Windows_7_Support to join a SME Server 8.0 Domain with Win7.
The sme-server gave a welkom at the join. I have reboot my windows 7 client and log on again and close it. But I can't find any data in the profiles folders of the sme server.

Do I miss something?  Could you help me with a suggestion?

Gert-Jan

you should take a look into logs (/var/log/messages, /var/log/samba/*, /var/log/smbd/*, /var/log/nmbd/*) searching for errors..

[gjverheij]

Thanks for reaction, I have found some problems:

message:

Apr 27 17:02:35 spijksterriet esmith::event[1971]: Processing event: machine-account-create uitbouw2$
Apr 27 17:02:35 spijksterriet esmith::event[1971]: Running event handler: /etc/e-smith/events/machine-account-create/S10create-machine-account
Apr 27 17:02:35 spijksterriet /etc/e-smith/events/machine-account-create/S10create-machine-account[1972]: /home/e-smith/db/accounts: OLD uitbouw2$=(undefined)
Apr 27 17:02:35 spijksterriet /etc/e-smith/events/machine-account-create/S10create-machine-account[1972]: /home/e-smith/db/accounts: NEW uitbouw2$=machine
Apr 27 17:02:35 spijksterriet /etc/e-smith/events/machine-account-create/S10create-machine-account[1972]: /home/e-smith/db/configuration: OLD MinUid=5012
Apr 27 17:02:35 spijksterriet /etc/e-smith/events/machine-account-create/S10create-machine-account[1972]: /home/e-smith/db/configuration: NEW MinUid=5014
Apr 27 17:02:35 spijksterriet /etc/e-smith/events/machine-account-create/S10create-machine-account[1972]: /home/e-smith/db/accounts: OLD uitbouw2$=machine
Apr 27 17:02:35 spijksterriet /etc/e-smith/events/machine-account-create/S10create-machine-account[1972]: /home/e-smith/db/accounts: NEW uitbouw2$=machine|Uid|5013
Apr 27 17:02:35 spijksterriet esmith::event[1971]: create-machine-account uitbouw2$: Creating Unix user and group 
Apr 27 17:02:35 spijksterriet esmith::event[1971]: Locking password for user uitbouw2$. 
Apr 27 17:02:35 spijksterriet esmith::event[1971]: passwd: Success 
Apr 27 17:02:35 spijksterriet esmith::event[1971]: Group uitbouw2$ successfully added! 
Apr 27 17:02:35 spijksterriet esmith::event[1971]: User uitbouw2$ successfully added! 
Apr 27 17:02:35 spijksterriet esmith::event[1971]: create-machine-account uitbouw2$: Locking account 
Apr 27 17:02:35 spijksterriet esmith::event[1971]: User uitbouw2$ successfully modified! 
Apr 27 17:02:35 spijksterriet esmith::event[1971]: create-machine-account uitbouw2$: Creating smbpasswd account 
Apr 27 17:02:35 spijksterriet esmith::event[1971]: Added user uitbouw2$. 
Apr 27 17:02:35 spijksterriet esmith::event[1971]: S10create-machine-account=action|Event|machine-account-create|Action|S10create-machine-account|Start|1398610955 127067|End|1398610955 840357|Elapsed|0.71329
Apr 27 17:02:35 spijksterriet esmith::event[1971]: Running event handler: /etc/e-smith/events/machine-account-create/S95ldap-update-simple
Apr 27 17:02:37 spijksterriet esmith::event[1971]: S95ldap-update-simple=action|Event|machine-account-create|Action|S95ldap-update-simple|Start|1398610955 841330|End|1398610957 57616|Elapsed|1.216286
Apr 27 17:02:37 spijksterriet smbd[1970]: [2014/04/27 17:02:37.079956,  0] passdb/pdb_smbpasswd.c:665(add_smbfilepwd_entry)
Apr 27 17:02:37 spijksterriet smbd[1970]:   add_smbfilepwd_entry: entry with name uitbouw2$ already exists
Apr 27 17:02:40 spijksterriet smbd[1970]: [2014/04/27 17:02:40.472321,  0] rpc_server/netlogon/srv_netlog_nt.c:976(_netr_ServerAuthenticate3)
Apr 27 17:02:40 spijksterriet smbd[1970]:   _netr_ServerAuthenticate3: netlogon_creds_server_check failed. Rejecting auth request from client UITBOUW2 machine account UITBOUW2$
Apr 27 17:04:09 spijksterriet smbd[1999]: [2014/04/27 17:04:09.264175,  0] rpc_server/netlogon/srv_netlog_nt.c:976(_netr_ServerAuthenticate3)
Apr 27 17:04:09 spijksterriet smbd[1999]:   _netr_ServerAuthenticate3: netlogon_creds_server_check failed. Rejecting auth request from client UITBOUW2 machine account UITBOUW2$
Apr 27 17:21:14 spijksterriet esmith::event[2415]: Processing event: machine-account-create snelle-jongen$
Apr 27 17:21:14 spijksterriet esmith::event[2415]: Running event handler: /etc/e-smith/events/machine-account-create/S10create-machine-account
Apr 27 17:21:14 spijksterriet /etc/e-smith/events/machine-account-create/S10create-machine-account[2416]: /home/e-smith/db/accounts: OLD snelle-jongen$=(undefined)
Apr 27 17:21:14 spijksterriet /etc/e-smith/events/machine-account-create/S10create-machine-account[2416]: /home/e-smith/db/accounts: NEW snelle-jongen$=machine
Apr 27 17:21:14 spijksterriet /etc/e-smith/events/machine-account-create/S10create-machine-account[2416]: /home/e-smith/db/configuration: OLD MinUid=5014
Apr 27 17:21:14 spijksterriet /etc/e-smith/events/machine-account-create/S10create-machine-account[2416]: /home/e-smith/db/configuration: NEW MinUid=5023
Apr 27 17:21:14 spijksterriet /etc/e-smith/events/machine-account-create/S10create-machine-account[2416]: /home/e-smith/db/accounts: OLD snelle-jongen$=machine
Apr 27 17:21:14 spijksterriet /etc/e-smith/events/machine-account-create/S10create-machine-account[2416]: /home/e-smith/db/accounts: NEW snelle-jongen$=machine|Uid|5022
Apr 27 17:21:14 spijksterriet esmith::event[2415]: create-machine-account snelle-jongen$: Creating Unix user and group 
Apr 27 17:21:14 spijksterriet esmith::event[2415]: Locking password for user snelle-jongen$. 
Apr 27 17:21:14 spijksterriet esmith::event[2415]: passwd: Success 
Apr 27 17:21:14 spijksterriet esmith::event[2415]: Group snelle-jongen$ successfully added! 
Apr 27 17:21:14 spijksterriet esmith::event[2415]: User snelle-jongen$ successfully added! 
Apr 27 17:21:14 spijksterriet esmith::event[2415]: create-machine-account snelle-jongen$: Locking account 
Apr 27 17:21:14 spijksterriet esmith::event[2415]: User snelle-jongen$ successfully modified! 
Apr 27 17:21:14 spijksterriet esmith::event[2415]: create-machine-account snelle-jongen$: Creating smbpasswd account 
Apr 27 17:21:14 spijksterriet esmith::event[2415]: Added user snelle-jongen$. 
Apr 27 17:21:14 spijksterriet esmith::event[2415]: S10create-machine-account=action|Event|machine-account-create|Action|S10create-machine-account|Start|1398612074 46927|End|1398612074 660916|Elapsed|0.613989
Apr 27 17:21:14 spijksterriet esmith::event[2415]: Running event handler: /etc/e-smith/events/machine-account-create/S95ldap-update-simple
Apr 27 17:21:15 spijksterriet esmith::event[2415]: S95ldap-update-simple=action|Event|machine-account-create|Action|S95ldap-update-simple|Start|1398612074 661732|End|1398612075 735501|Elapsed|1.073769
Apr 27 17:21:15 spijksterriet smbd[2414]: [2014/04/27 17:21:15.751339,  0] passdb/pdb_smbpasswd.c:665(add_smbfilepwd_entry)
Apr 27 17:21:15 spijksterriet smbd[2414]:   add_smbfilepwd_entry: entry with name snelle-jongen$ already exists
Apr 27 17:21:19 spijksterriet smbd[2414]: [2014/04/27 17:21:19.529717,  0] rpc_server/netlogon/srv_netlog_nt.c:954(_netr_ServerAuthenticate3)
Apr 27 17:21:19 spijksterriet smbd[2414]:   _netr_ServerAuthenticate3: failed to get machine password for account SNELLE_JONGEN$: NT_STATUS_NONE_MAPPED
Apr 27 17:21:19 spijksterriet smbd[2414]: [2014/04/27 17:21:19.538227,  0] rpc_server/netlogon/srv_netlog_nt.c:954(_netr_ServerAuthenticate3)
Apr 27 17:21:19 spijksterriet smbd[2414]:   _netr_ServerAuthenticate3: failed to get machine password for account SNELLE_JONGEN$: NT_STATUS_NONE_MAPPED
Apr 27 17:22:40 spijksterriet smbd[2443]: [2014/04/27 17:22:40.751878,  0] rpc_server/netlogon/srv_netlog_nt.c:976(_netr_ServerAuthenticate3)
Apr 27 17:22:40 spijksterriet smbd[2443]:   _netr_ServerAuthenticate3: netlogon_creds_server_check failed. Rejecting auth request from client SNELLE-JONGEN machine account SNELLE-JONGEN$ 

samba:
[2014/04/27 17:22:40.751878,  0] rpc_server/netlogon/srv_netlog_nt.c:976(_netr_ServerAuthenticate3)
  _netr_ServerAuthenticate3: netlogon_creds_server_check failed. Rejecting auth request from client SNELLE-JONGEN machine account SNELLE-JONGEN$
[2014/04/27 19:29:16.713469,  0] rpc_server/netlogon/srv_netlog_nt.c:976(_netr_ServerAuthenticate3)
  _netr_ServerAuthenticate3: netlogon_creds_server_check failed. Rejecting auth request from client SNELLE-JONGEN machine account SNELLE-JONGEN$

So I see a problem, but what to do? Who could help me further?

[twijtzes]

I found slow logins to be the cause of the problems in my case. I also installed windows_samba_performance.reg from the resources directory. Did you ?


In the end still struggling user profiles and with MS office packages (MSoffice 2013). Maybe switch off roaming profiles and copy relevant data into users directory ....

Good luck

[brianr]

I found slow logins to be the cause of the problems in my case. I also installed windows_samba_performance.reg from the resources directory. Did you ?


In the end still struggling user profiles and with MS office packages (MSoffice 2013). Maybe switch off roaming profiles and copy relevant data into users directory ....

Good luck

You do realise that Office 2003 (along with WIndows XP) is no longer "supported" by Microsoft?  So no security updates will be made, consequently it is only a matter of time before an exploit comes along which will take down any PC running Office 2003.

Oops - sorry I mis-read your posting - Office 2013 is fine AFAIK

[twijtzes]

True,

However, I am talking about the 2013 office version, also known as the server breaker

[idp_qbn]

gjverheij (and others)

Do your users actually "roam" from PC to PC.
If they do not, then avoid roaming profiles like the plague.

Anything a user saves on the Desktop becomes part of their profile. If the have roaming profiles, then the profile is loaded over the network from the server - including all those things they have saved to the desktop. I have seen people with profiles of 100Mb - they took several minutes (well, more than 2) to complete the logon, from entering the password to being able to work.

Sometimes , the process would time-out and the user would get a message asking if they wanted to use a stored copy of a local profile - which could be an old one, or could create a second profile, or ...... or something else Microsoft dreamed up.

At the end, if they have made a change to their profile (including editing a file that is on the desktop) then the whole profile is saved back to the server when they logout. Imagine the traffic when 20 people try to logon at the same time.......

And that's all the advice I can give. Sorry I can't be more helpful.

Ian

[twijtzes]

Thanks Ian,

What happens to the (sme-stored) profiles once i switch off roaming profiles. It could be usefull to get some of the data to the local profiles.

Thanks,
Taco

[janet]

twijtzes

Take a look in /home/e-smith/files/samba/profiles/.....

[janet]

gjverheij

At the latest moment I change to windows 7.

Changed from what ?
Were you running an earlier version of Windows previously that was joined to the sme server Domain ?
There was a change after Win XP, where the profiles are stored as .../username.V2, so you will not see data from the older profiles stored as .../username only.

Did you enable Roaming profiles in server manager ?

Keep in mind if you want to use Roaming profiles, the hardware & settings & installed software etc should ideally be the same on all workstations.
Also you need to do appropriate configuration of the workstations to prevent users creating large file size bloated profiles that will cause long login delays etc.

Also you should unjoin old workstations that have same names & users, & reset your workstation to be a Workstation member with a different name rather than a DOMAIN member.
Then after a restart, you can then change your workstation to be a DOMAIN member using the new (different) DOMAIN name.