10.4.11 = 10.5.6 migration: preserving samba domain

Hi,
I'm trying to follow OSX server migration path from tiger to leopard as described in document "Upgrading and Migrating v10.5 2nd ed" and to preserve as much data as possible in OpenDirectory and Windows services (samba). OpenDirectory migration looks ok, user accounts and passwords are there, although preferred method looks like not using Server Admin GUI to Import OD archive after creating fresh master (creating fresh master also creates new samba SID in OD and import does not override it), but rather using command line version "slapconfig -restoredb ODArchive.sparseimage" (do not use pass when creating the archive or it will hang mounting the sparseimage file forever..)
However, preserving samba domain seems impossible. On a fresh 10.5.6 server installation after importing OD with slapconfig and checking everything is in place (SID info is correctly restored in CIFSServer record, Config section in OD), copied tiger /etc/smb.conf into leopard /etc/smb.conf.old and tried running script:
/System/Library/ServerSetup/MigrationExtras/70_smbconfigmigrator
which failed when executing:
/usr/bin/opendirectorypdbconfig -c update
unable to open file (No such file or directory)
no credentials available
opendirectorypdbconfig error (-14098)
smb:command = "upgradeConfig"
SMB service config in Server Admin looks ok, samba starts, but doing "net getlocalsid" returns completely new domain SID, so domain is lost and all user profiles are lost too. Is that possible at all, to preserve samba domain when migrating to leopard ?
Thanks,

Ok, have read in full (several times actually) and then tried - it works, excellent! Just had to run an additional little thing after step 10) - "net setlocalsid SID", so to resume:
- use Server Admin GUI tool (create fresh master with same settings first) to import 10.4 OD archive;
- don't forget to "mkpassdb -kerberize" after import;
- create fresh PDC config (and do not use 70_smbconfigmigrator);
- restore the good SID in 3 places: "net setdomainsid SID", "net setlocalsid SID" and OD Config/CIFSServer record;
Thanks a lot !

Similar Messages

Migrating multiple domains with same name - how? Rename? Migrate through temporary domain?

Hi,
we have acquired another company, and they have multiple, separate domains with the same name (every site has a domain with NetBIOS name "COMPANY" and DNS name "company.local"). Now we want to migrate all these domains into ours using
ADMT.
Unfortunately, we did not manage to migrate one of these domains completely, so the trust must remain established for some time. But we have to continue with the second domain - which normally would require a trust, but of course we can't establish a trust
to two domains with the same name at the same time.
I found two potential solutions for the dilemma, but I'm not sure if both are reasonable:
1) Rename the domain with RENDOM.EXE to COMPANY2 and company2.local and then migrate with ADMT
2) Migrate COMPANY to a temporary domain such as COMPANYTEMP and then migrate from COMPANYTEMP to our domain
Given that there are roughly 100 users, 2 domain controllers and 8 other servers, what would be the better approach? Is option 2 possible at all, so would I be able to use the sidHistory attribute migrated from the original COMPANY domain in our domain at
all?
There is also an Exchange 2007 server, which seems to make option 1 impossible unless we find another way to migrate it (like, export all mailboxes to PST before migration) ...

Ok, that's what I expected. Still, I have servers in the old domain, so if I do these steps:
first create a new temporary domain i.e COMPANYTEMP and
create trust between COMPANYTEMP -
COMPANY(Right)
then do the migration with sidHistory from COMPANY(right) --> COMPANYTEMP ,
disconnect the domain COMPANY(right) ,
users will lose connectivity to any servers in the domain. I understand that it does not work with all domains connected? Of course I can't make OURCOMPANY's domain controllers see the DCs of COMPANY (right) in DNS (though I could achieve it the other way
round).
My original plan was:
first create a new temporary domain i.e COMPANYTEMP and
create trust between COMPANYTEMP -
COMPANY(Right)
then do the migration with sidHistory from COMPANY(right) --> COMPANYTEMP ,
create trust between OURDOMAIN and COMPANYTEMP
then do the migration with sidHistory from
COMPANYTEMP --> OURDOMAIN,
Migrate users
Migrate computers
Migrate servers
remove trusts and old domain
But I see that this will not work out, right? So, my only option would be:
first create a new temporary domain i.e COMPANYTEMP and
create trust between COMPANYTEMP -
COMPANY(Right)
then do the migration with sidHistory from COMPANY(right) --> COMPANYTEMP ,
Migrate computers and servers to COMPANYTEMP
Install new Exchange server in COMPANYTEMP
migrate mailboxes to COMPANYTEMP
disconnect / abandon COMPANY(right)
create trust between OURDOMAIN and COMPANYTEMP
then do the migration with sidHistory from COMPANYTEMP
--> OURDOMAIN,
Migrate users
Migrate computers
Migrate servers
Migrate mailboxes
remove trusts and old domain
And to minimize user impact, all this would have to be done in one go (over night), which is hardly possible .........................

Issue in SQL-server migration to new domain

Hello,
I have a scenario, where i need to migrate SQL 2005 servers db's ( around 30, small ones) to new server in a new domain. Destinationserver is 2012 R2, running SQL2014
Domains have trust between them, and users have already been migrated to new domain. Users are using the databases with NT authing from the new domain (new logins & users have been created to old sql-server).
I have backed up db's from old server and restored them in new server. After that, i restored logins with following article's script:
http://support.microsoft.com/kb/918992
I cleaned from the login script logins that are not in use, change the domainname to new in CREATE LOGIN phase (for the users who did not have already login from new domain) and the script ran without errors.
User Mappings are like they should be on logins, however, the user & schema names are indicating to old domain. If i try to change them, i receive error about SID mismatch. This affects also users, who have already had new logins for new domain, their
usernames on mappings are also changed to old domain's username. What is causing this?

Hi,
Could you try the following to migrate the logins and check the result?
1. You may drop all the windows login. Modify the script generated by sp_help_revlogin step and replace create login
to drop login.
2. Use the script generated by sp_help_revlogin step to create
Logins. Modify login name to accommodate new domain name.
3. Grant server level roles using the output from:
Generate Server level role related info :
SELECT 'EXEC sp_addsrvrolemember ''' +
p.name + ''' , ''' + r.name + ''';'
FROM
sys.server_principals r
INNER JOIN sys.server_role_members m ON r.principal_id = m.role_principal_id
INNER JOIN sys.server_principals p ON
p.principal_id = m.member_principal_id
WHERE
r.type ='R'
Sample Output :-
EXEC sp_addsrvrolemember 'sa' , 'sysadmin';
4. Map the SIDS using below command for all DB by using ALTER USER. For example:
ALTER USER [DomainA\UserA] with login = [DomainB\UserA]
See:
http://blogs.technet.com/b/mdegre/archive/2011/06/27/can-i-move-sql-server-to-another-domain.aspx
Here some useful articles:
http://www.databasejournal.com/features/mssql/article.php/3922256/Re-generating-SQL-Server-Logins.htm
http://support.microsoft.com/kb/918992/en-us
http://support.microsoft.com/kb/240872
Thanks.
Tracy Cai
TechNet Community Support

Migrating from 2003 domain/forest level to 2008R2 with all DC's at 2008R2 and 2 other Domain External and Forest Trusts

Is there anything that needs to be done or considered when migrating from 2003 domain/forest level to 2008R2 with all DC's at 2008R2 with 2 other 2003 separate Domain incoming
and outgoing Trusts, one Trust that is a Forest Trust and the other is an External Trust? Is there any chance or risks that doing this upgrade will break either one of these Trust relationships? Some of the user accounts with SID history have been migrated
from both Domain Trusts to our domain. Any chance that this upgrade will break these relationships for users that are using SID history for access to folders and files in their old Domains? If so what can be done to protect these trusts and SID history, prior
to moving the Domain to 2008R2

Hi,
Based on my knowledge,
the Upgrade of the function level do not affect the trust relationship.
Besides, before you upgrade the Functional Level,
verify that all DCs in the domain are, at a minimum, at the OS version to which you will raise the functional level.
Once the Functional Level has been upgraded, new DCs on running on downlevel versions of Windows Server cannot be added to the domain or forest.
For more information about function level, we can refer to following links:
Understanding Active Directory Domain Services (AD DS) Functional Levels
http://technet.microsoft.com/en-us/library/understanding-active-directory-functional-levels(v=ws.10).aspx
What is the Impact of Upgrading the Domain or Forest Functional Level?
http://blogs.technet.com/b/askds/archive/2011/06/14/what-is-the-impact-of-upgrading-the-domain-or-forest-functional-level.aspx
Best Regards,
Erin

Subincacl tool with netapp cifs migration to new domain

Hello
I have DomainA (old) DomainB (new). i am migrating services from DomainA. to DomainB. i have a netapp filer running CIfS in DomainA. i have two way trust between two doamins. All the security groups have been migrated from DomainA
to DomainB with sid history via Quest tool . now i need to repermission ntfs on all the shares with DomainB. I tried usign subinacl tool with following syntax without success
subinacl /outputlog=c:\output.txt /errorlog=c:\error.txt /subdirectories Z:* /migratedomain=domainA=DomainB=MAPFILE.TXT
where mapfile has a a mapping of between groups of DomainA and DomainB, Z is mapped drive to netapp cifs volume
but it errored out with following
Last Syntax Error:WARNING : /migratedomain=DomainA=DomainB=mapfile.txt : Invalid option : Z:\*

Hi,
Do you run the command from an elevated command prompt? Verify you have proper permission for the mapped drive. Please use the following version of SubInACL.
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=23510
For domain migration:
SubinAcl /noverbose /subdirectories x:\*.* /changedomain=DomainA=DomainB
For server migration:
SubinAcl /subdirectories \\Destserver\Share\*.* /migratedomain=SourceServer=DestServer
Best Regards,
Aiden
Aiden Cao
TechNet Community Support

Domain Migration :from single domain to multiple domain.

Hi ,
We have an urgent requirement for the domain migration
The scenario is currently we are using MS AD as LDAP server to store portal users and thier credentials.
Lets say we have current domain name as : ad.abc.com
we are planning to migrate from this domain to number of domains.our requirement is to move the portal users into thier specific domain in batches.eg out of 5 users 2 has been moved to new domain and other 3 are still in ad.abc.com.
But after domain migration ,all the 5 users <b>should</b> be able to access all the applications and functionality of portals.
What should we do to achieve the same?
How portal applications will be affected by this?Can all the users access all applications without fail?
What exactly the LDAP does in portals?
Any help will be greatly appreciated
Thanks in Advance
Amit

Hi,
Yes, you need to prepare Active Directory and domains.
What's more, you need to upgrade existing Exchange 2007 servers to Exchange 2007 Service Pack 2 at least.
Here is an article for your reference.
Exchange 2007 - Planning Roadmap for Upgrade and Coexistence
http://technet.microsoft.com/en-us/library/dd638158(v=exchg.141).aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Domain migration: From single domain to Multiple

Hi ,
We have an urgent requirement for the domain migration
The scenario is currently we are using MS AD as LDAP server to store portal users and thier credentials.
Lets say we have current domain name as : ad.abc.com
we are planning to migrate from this domain to number of domains.our requirement is to move the portal users into thier specific domain in batches.eg out of 5 users 2 has been moved to new domain and other 3 are still in ad.abc.com.
But after domain migration ,all the 5 users should be able to access all the applications and functionality of portals.
What should we do to achieve the same?
How portal applications will be affected by this?Can all the users access all applications without fail?
What exactly the LDAP does in portals?
Any help will be greatly appreciated
Thanks in Advance
Amit

Hi,
Yes, you need to prepare Active Directory and domains.
What's more, you need to upgrade existing Exchange 2007 servers to Exchange 2007 Service Pack 2 at least.
Here is an article for your reference.
Exchange 2007 - Planning Roadmap for Upgrade and Coexistence
http://technet.microsoft.com/en-us/library/dd638158(v=exchg.141).aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

File associations are lost when user account is migrated from one domain to another domain (SID changes)

Hello,
Currently we are in the middle of a migration project. We are migrating users from child domains to the root domain of one organization.
The user accounts are migrated with powershell using Move-ADObject cmdlet. This works as expected. The SIDHistory attribute is updated correctly.
Recently we received complaints from some *migrated* users - they lost their default/custom file associations. This happens only on Windows 8/Windows 8.1.
What happens:
the user is migrated and logs on
her profile loads and everything's preserved (as expected)
the user clicks on a .jpeg file (previously associated with program XYZ)
OS asks the user to choose a program to open the file with
the user chooses a default program XYZ and the file opens
when the user clicks on a .jpeg file again - OS asks to choose a program again
i.e. the settings are not preserved.
Our investigation shows that it is connected with the UserChoice registry key and the HASH value under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.SomeExt
According to this blog
the HASH is calculated based on user's SID. But after the migration the user has new SID and the HASH becomes invalid and we hit this:
"However In Win 8, the registry changes are verified by a hash (unique per user and app) that detects tampering by apps. In the absence of a valid hash, we ignore the default in the registry."
Currently deleting the UserChoice key for all associations solves the problem. But the user has to make all her customizations again which is undesirable.
Is there any supported way to fix this? Why the OS doesn't update the HASH after the first logon when the SID has changed as it updates the SID for the ProfileList key?
This could become big issue in large migrations.

Hello Petar K. Georgiev,
Please check the following article to change the registry key to change back to the default file type associations.
http://www.sevenforums.com/tutorials/19449-default-file-type-associations-restore.html
Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Best regards,
Fangzhou CHEN
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Exchange Migration from One domain to another domain on same forest

Team,
we are in the process of migrating exchange infrastructure from one child domain to another child domain within same forest.
root domain - root.com
child domains - US.root.com and EMEA.root.com
EMEA and US Domains setup are different from each other. Like EMEA has different email address policy , Email Flow than US , connectors etc.
Now we need to migrate all emea users under US Domain. based on the geographical locations, we are building a new dc, mailbox , cas servers on EMEA location , but these servers will be part of US Domain.
for CAS Servers - we are planing to register respective sites ( site affinity), so all the local requests will be handled by new cas server which is built under US Domain.
Mailbox Servers - we would be creating new db's and the limits on new mbx server and going to replicate as its on EMEA Mailbox server.
can some one please let us know what are the precautions , recommendation, sequence which we need to follow to perform smoother migration. as of now , I can think of below topics.
Mailbox Migration -I Have a script , which
will take care of mailbox movement once the objects are being moved.
Contacts Migration - Willard Martin blog helped me to perform migration
DL Migration - I believe there is no mechanism to migrate DL. only option is to recreate.
Email address Policy:we would be creating a new address policy and apply to OU's
DB Consistency check – do we have to perform the health checks on source mailbox server to see , the servers are free from errors /corruption.
Check outlook configuration - After the migration, we need to check and see , the exchange server/ auto discover works and identify the new exchange servers.
Internal /External Email flow.-
Active Sybc , OWA
Public folder Migration -
Offline Address Book
Certificates
any help or suggestions would be great.
Srinivasa K

Hi Srinivasa,
According to your description, I think you have done all the preparation.
For DL migration, the following article may give your some hints:
How to Migrate Distribution Groups Across a Forest
Good Luck!
Niko Cheng
TechNet Community Support

AD User migration to new domain

I have SharePoint site in Domain A with 1000 users. There will be new domain B setup. I need to migrate ShrePoint Site from domain A to domain B. The AD users SID will remain the same. Below are two possible solution
1. Install new SharePoint in Domain A. Restore the site from Domain A to Domain B. Migrate all 1000 users using move-Spuser or Stsadm command.
2. Change the domain for System hosting SharePoint. Then migrate the 1000 users using move-Spuser or Stsadm command
Will the permission remains same in case user is migrated or what can be other issues.
Please remember to mark the replies as answers or vote as helpful if they help.

So one thing to keep in mind is that disjoining/joining SharePoint farms from one domain to another isn't supported. Instead, the general process is to build a new farm in the target domain and recreate it, restoring backups of content/service application
databases as necessary.
Users cannot be moved from one domain to another without a SID change. Part of their SID stems from the domain they're a member of, and that changes when they're moved. There is a function called SIDHistory which stores previous SIDs from previous domains,
and this is commonly used. Despite that, you still need to issue a Move-SPUser, not only because their SID has changed, but because their domain name has changed.
One thing to note is that if you're using a Claims-enabled Web Application, you still must issue -IgnoreSID in the Move-SPUser cmdlet, regardless if SIDHistory is used or not during the migration.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Migration windows 2003 domain controller

how to migrate windows server 2003 domain controller to windows server 2008/2012

Generally you would stand up the new server, join it to existing domain, dcpromo it and transfer the roles over.
You can follow along on Meinolf's page.
http://blogs.msmvps.com/mweber/2012/07/30/upgrading-an-active-directory-domain-from-windows-server-2003-or-windows-server-2003-r2-to-windows-server-2012/
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

AD Migration from one domain to another domain between different Forest.

Dear Team,
We have a domain named "test.gov.in" .Now we want migrate all the users,computers,groups,GP ....etc in to our new domain "abc.net".Operating system of the source DC and destination Dc is same (Windows 2003 32 bit)..
Pls provide me the steps to migrate one domain to another domain between different forest
Thanks
Anurag

Would agree with Christoffer and migrate using ADFS but before you can do this you will need to set up a trust between the two domains. Once this has been accomplished then you can run ADMT.
http://technet.microsoft.com/en-us/library/cc740018(v=WS.10).aspx
Downloading ADMT is a free tool from Microsoft
http://www.microsoft.com/en-us/download/details.aspx?id=8377
ADMT Guide
http://www.microsoft.com/en-us/download/details.aspx?id=19188
Paul Bergson
MVP - Directory Services
MCITP: Enterprise Administrator
MCTS, MCT, MCSE, MCSA, Security, BS CSci
2012, 2008, Vista, 2003, 2000 (Early Achiever), NT4
Twitter @pbbergs http://blogs.dirteam.com/blogs/paulbergson
Please no e-mails, any questions should be posted in the NewsGroup.
This posting is provided AS IS with no warranties, and confers no rights.
I think you mean ADMT and not ADFS :)
Enfo Zipper
Christoffer Andersson – Principal Advisor
http://blogs.chrisse.se - Directory Services Blog

Migrate to new domain and new SCCM

The migration scenario is this:
All Clients are in Domain1 and are managed through SCCM 2012 with System Center Endpoint Protection 2012.
Some of the clients need to join a new domain and be managed through a new SCCM 2012 R2 server with System Center Endpoint Protection 2012 R2.
There are no trusts between the forests. Do we need to uninstall the SCCM 2012 Agent and SCEP 2012 and then install the new SCCM 2012 R2 Agent and SCEP 2012 R2?
Or can we just uninstall SCCM 2012 Agent only and keep SCEP 2012 and later install.

There are multiple ways to go about it.
Assuming that the AD forest is properly extended and the new site's info is properly published, then you can simply run a script:
http://msdn.microsoft.com/en-us/library/cc146558.aspx
http://gallery.technet.microsoft.com/scriptcenter/Change-sccm-configmgr-cf6e0327/view/Discussions
If the two assumptions above aren't correct, then the client has no way of getting the trusted root key gracefully for the new site and running ccmsetup is the best way.
The ccmsetup bootstrapper will download files as needed from the closest DP but (from memory) won't redownload files if they are already present in the ccmsetup folder.
A client push is probably the easiest method to initiate ccmsetup because it can be managed from a central location -- just make sure you select the checkbox for always reinstall. Of course, as mentioned above, if someone has previously used the "group
policy" to assign the site to your clients, you'll need to clean up that mess first otherwise the clients will always try to assign to the old site.
Jason | http://blog.configmgrftw.com

Migrating one email domain to external server

our AD domain "domain1.com" users have @domain1.com, @domain2.com, and @domain3.com (this one is for testing usage) mailboxes/addresses on our internal Exchange 2010 14.01.0438.000 server. All users are on the same domain regardless
of the email address they use. mailboxes with @domain1.com as their primary smtp address are being migrated to an email service outside of our organization/domain but will still remain users on our domain. For those users we'll be creating a new
profile in Outlook pointed at that new external mail server to switch over to on the cutover date while leaving the existing profile as is. Following migration for a period of time we want @domain1.com users to still be able revert to their current
Outlook profile and be able to get to our OWA in case any problems/inconsistencies occurred migrating contents to the new service. It's understood that sending/receiving mail would no longer work for them on the internal Exchange server, the point is just
that they could access the old contacts/calendar/notes/tasks/emails.
My testing with migrating @domain3.com indicated that in order for domain2.com senders to be able to send mail to @domain1.com recipients after the cutover date and have the mail arrive at the external server instead of the internal server, the following
would have to be done:
-domain1.com removed from gatewayproxy attribute in recipient polices -
removal of gatewayProxy via ADSI
-domain1.com removed from exchange >> organization configuration >> hub transport >> accepted domains
-mx record pointing at external mail server added to internal dns server domain1.com zone
-domain1.com removed from smtp proxyAddresses attribute on each mailbox
It seems like there should be a way to achieve the result of getting the mail to the external server without modifying the proxyAddresses attributes so that the users could still get back into the old exchange server after cutover with their original address.
any ideas?
Thanks

the steps to get [email protected] to [email protected] mail sent to external server are clear from testing and additional testing shows some option for still getting into the old mailboxes from clients/owa but not clear is how it could be done while leaving
domain1.com mailbox addresses intact on the old Exchange server and the AD user object 'mail' attribute intact as it was pre-cutover. To expand and rephrase my original post, is there a way to make Exchange determine whether it should route domain1.com
mail internally vs externally via a global setting that would take priority over and cause to be ignored smtp proxyAddresses attributes on individual mailboxes so these don't have to be stripped/modified causing unwanted AD attribute alteration?
objective partially achieved -
AD object for [email protected] mailbox has the following attributes -
proxyAddresses = SMTP:[email protected] (Exchange primary reply-to address) & smtp:[email protected]
'mail' attribute = [email protected]
if we change primary/reply SMTP in exchange to [email protected] and remove SMTP:[email protected], the result of internal mail sent to [email protected] going to the external server is accomplished but the 'mail' attribute in AD then changes to [email protected]
which is unwanted. we still want 'mail' attribute left as is for these users since their email addresses are not changing. access to mailbox contents on old exchange server via old [email protected]'s old outlook profile + OWA still work which
is good though.
also found that adding a domain to organization configuration >> hub transport >> accepted domains as 'external relay' in addition to a send connector for the domain pointed at the MX for the external server still isn't enough to override/ignore
any proxyaddresses on the internal mailboxes. mail willl still end up at the internal mailbox.

Migrate servers between domains

Hello
We need to plan an AD domain migration to an already existing domain - i.e. not a new domain - for dozens of servers hosting different roles and am looking for some general pointers for what we should be aware of.
We cannot use ADMT (for internal political reasons) and cannot use external tools, e.g. Quest (for cost reasons)
The roles on the servers include:
Domain controllers, IIS, SQL, CRM, VMWare Virtual Center - plus other bespoke applications.
I know there will NOT be a "one size fits all" process for every server (or even every application) but was hoping someone could provide general information for the apps mentioned above.
e.g. should we not even consider moving the server(s) between domains but rather build a new server and reinstall the application ? If rebuilding a server is NOT an option for any reason, CAN we move the application server(s) to the
other domain without issues ?
I realise this is a very complex set of tasks but, as I said, just looking for some general information to give us a starting point.
Thanks

>>>CAN we move the application server(s) to the other domain without issues ?
It depends on your authentication and permission model. Where are the users and groups? ACL on these servers from a different domain?
Please provide more information.
Santhosh Sivarajan | Houston, TX | www.sivarajan.com
ITIL,MCITP,MCTS,MCSE (W2K3/W2K/NT4),MCSA(W2K3/W2K/MSG),Network+,CCNA
Windows Server 2012 Book - Migrating from 2008 to Windows Server 2012
Blogs: Blogs
Twitter: Twitter
LinkedIn: LinkedIn
Facebook: Facebook
Microsoft Virtual Academy:
Microsoft Virtual Academy
This posting is provided AS IS with no warranties, and confers no rights.

10.4.11 = 10.5.6 migration: preserving samba domain

Similar Messages

Maybe you are looking for