Koozali.org: home of the SME Server
Obsolete Releases => SME Server 9.x => Topic started by: plobek on January 06, 2017, 02:03:36 PM
-
I installed SME 9.1. Yum update. Installed e-smith-samba-2.4.0-23.el6.sme.noarch. Applied patch for win10 samba and samba performance. Edited netlogon.bat to take time from server, map \home drive and other Ibays at login. Windows 10 is joining domain. After reboot and when I try login to domain with user I am being logged into temporary profile. When I check drives, ones I point to be mapped are there. When check ".V6" profile on server I can see all files (Desktop, Downloads, ect.).
Windows 7 PRO machines joining domain with no problem, user can log into their profiles.
I have done everything the same way I have been doing for the first when I was installing SME for the first time. All was working, now not. Need to upgrade all PCs on site to W10 but at the moment this is not possible because we can not use SME as DC.
P.S.
Problem occur no matter if this is fresh Win 10 install or upgrade from Win 7.
EDIT 1:
When I create a folder on Desktop, put files in it, then log off, log in they are still there. Under ".V6" I can see them too.
EDIT 2:
Forgot to mention that Win 10 PRO is with anniversary updates+ latest patches
-
Are you using roaming profiles?
-
P.s. welcome here ;-)
-
Yes Domain Controller and Roaming Profiles, and Yes I now it is not best option but this is what people want from me.
-
ok.. your best bet is to take a look at windows event viewer and see if you've got any error..
moreover, check samba's logs on SME..
please report back everything you'll find, so we can try to help you, thank you
-
Because I was short of time and could not try find solution I reinstall SME 9.1 on the same machine. I know that this is not the best way to solve problems, because of time thing and not having other machine to install SME and leave it for investigation, I decided as above.
After fresh install I have done yum update, installed all updates from default repositories, edit /etc/e-smith/events/actions/user-create-profiledir" by adding a line "/home/e-smith/files/samba/profiles/${user}.V6"), create user account and everything is OK now. Any user can log in with no hassel.
You can close topic as unsolved. Thanks for any responses
-
Good.. You found the issue, they did it again
Would you please reporter your issue and your solution in bugzilla? Thank you
-
Sorry it may be a stupid newbie question but do you want me report this solution even if in my case there was noting serious I have done? All problems with "V6" profiles and windows anniversary update are in this bug report https://bugs.contribs.org/show_bug.cgi?id=9772 (https://bugs.contribs.org/show_bug.cgi?id=9772) and even I follow all instructions first stime I had my problem with temporary profile on Windows 10 and I do not have any other logs that I can add for a solution?
-
Sorry it may be a stupid newbie question
there are no supid questions :-)
but do you want me report this solution even if in my case there was noting serious I have done? All problems with "V6" profiles and windows anniversary update are in this bug report https://bugs.contribs.org/show_bug.cgi?id=9772 (https://bugs.contribs.org/show_bug.cgi?id=9772) and even I follow all instructions first stime I had my problem with temporary profile on Windows 10 and I do not have any other logs that I can add for a solution?
ok, I was on my smartphone and did not check bugzilla.. BTW, since you refer to a fixed/verified bug, you'd not have such an issue on an update system.. so, please, post in the bug your experience, thank you
-
plobek
You should report on that existing bug referred to, that you updated the e-smith-samba rpm to the version that claims to have fixed the v6 profile issue, but in your case it did not fix it.
Something could be wrong with the new rpm which needs fixing.
Users should not have to amend config files, so it appears there is still a bug, or perhaps something went wrong with the rpm upgrade or there is some other as yet unknown additional issue.