Moved from the Powerlink Lite users area.

At present Powerlink Lite users have no access to the forums but will be able to receive responses via the emails.

Julie
forums admin

a CIFS server unjoin/join or even a delete doesnt do anything to the file/dir ACLs that are stored in the data file systems

same as with a normal Microsoft server

right ...hopefully there is a trust between the domains ..or user accounts will actually reside in the same domain as the CIFS server.

yes, take a look at using server_cifs -Unjoin and server_cifs -Join command. The question is what's going to happen to permissions (ACL's) on the files currently mounted on this CIFS server.

Can one of you describe this process further or clarify for me?

We are collapsing a domain and I have one Celerra CIFS still resident on that collapsing domain. Short of unjoining and rejoining the new domain what other steps do I need to accomplish?

All users/OU/machines will be ADMT'd across... but won't usermapper only interpret the original domain and user reference?

I saw/found a server_cifs -Migrate command. Is this necessary?

There is a trust btwn the two but the thought is to completely terminate this domain.

Thanks for your attention.

Hello, I have been doing some testing on this.

I have created a CIFS server in domain1 and am attempting to move this CIFS server to domain2

I used the celerra manager to create the CIFS. Created interface, then assigned the CIFS server to it.

I then as istructed by support run the following commands

server_cifs server_2 -Unjoin compname=server1,domain=domain1,admin=myacct

the above is successful

I then run

server_cifs server_2 -Join compname=server1,domain=domain2,admin=myacct

this fails with Error 4020 : server_2 : failed to complete command.

Upon further incvestigation in Celerra manager I found the following event

SMB saveAccountPassword: Domain name mistmatch between 'cifs -add' and cifs -J' commands: domain1 - domain2

Does anyone know a way around this w/o completely rebuilding the CIFS server in the proper domain?

long shot in the dark but can you add this to your -Join command:

-o resetserverpasswd

so

server_cifs server_2 -Join compname=server1,domain=domain2,admin=myacct -o resetserverpasswd

When you create the computer account, you specify a domain as well, and that must match with the join command. You need go back one more step and re-create the cifs server with the new domain, then join the domain.

sagel, thanks.

it appears as though, as you mentioned, re-creating the CIFS server does it.

Our scope has changed a bit on this now and I'm wondering what you all can offer.

Basically we need to make data from on CIFS server in domain1 available to an already existent CIFS server in domain2.

I have since tested simply (via gui) unchecking in CIFS share properties the original CIFS server and selecting the new one (domain2) CIFS. This appears to work.

The gui however doens't confirm the adjustment (no suprise) and it is difficult to sift through my 18K+ shares to confirm.

Question 1 - can anyone confirm the appropriate steps for this considering I have mulitple shares to open up to this second CIFS server.

Question 2 - what is the syntax to simply see on specific CIFS server's shares/exports. server_export doesn't appear to have a way to show this.

Thanks.

server_cifs server_x will show you CIFS server details.

You can create 2 CIFS servers each in different domains and mount the same volume. Although the NTFS security will be the same, so the permission's must work in both domains (ie. trusted domains) If the domains are not trusted, I can't think of a way to share the same data in a windows environment.

is there a trust between these two domains ?



Do you need the shares on both CIFS servers or do you need to "move" them ?



it should - are you sure you pressed the GUI refresh icon (not the browser refresh) ?



a server_export should tell you nicely


what exactly do you want to do ?
how many shares ?



try "server_export server_2 -P cifs -list | sort +5"
or "server_export server_2 -P cifs -list | grep "

Yes the trust exists, and individuals and security groups have been migrated to the new domain as well.



I only need to move the shares to the second (newer) CIFS server. Although the old domain will be left as a resource domain the old CIFS server and exports can be destroyed



not sure if it was a timing issue, but the new shares finally listed with the secondary test system via the GUI


was this a joke?


approx two dozen need to be repointed at a different CIFS server (which happens to be in another domain)



lists all shares still



appears to not do anything, no errors either

Thanks for any further assitance. Really I'm just tryin to devise an easy transfer of these shares over to their new CIFS server. I can't seem to find any info that documents this for the Celerra skill deficient.

sorry, no. I was just thinking like a Unix guy
I realize 18k is a lot to manually sift through

Maybe this would work better for you to get an overview which shares are where
In the Celerra Manager CIFS share page select all shares by pressing -A
then right-click and select export data to export the share list into a csv files
using that with Excel you can then sort it there

approx two dozen need to be repointed at a different
CIFS server (which happens to be in another domain)

Question 2 - what is the syntax to simply see one specific CIFS server's shares/exports.
server_export doesn't appear to have a way to show this.

you are right there - there doesnt seem to be a server_export option for that - thats why I use Unix grep to filter
I'll file an enhancement request for that.

try "server_export server_2 -P cifs -list | sort +5"

lists all shares still

yes, but it should sort them according to which CIFS server they belong
(the +5 meaning to sort the lines according to the 5th field which normally is the netbios= field)

or "server_export server_2 -P cifs -list | grep "

appears to not do anything, no errors either

If you replace with the name of your CIFS server it should filter and show you only the shares belonging to that CIFS server
if you use "grep -v " instead it will show only shares not belonging to this CIFS server

If you use a different physical or virtual data mover you need to replace server_2 with the server name

Thanks for any further assitance. Really I'm just tryin to devise an easy transfer of these shares over
to their new CIFS server. I can't seem to find any info that documents this for the Celerra skill deficient.

If you know someone with Unix skills it isnt difficult to do a small skript that creates all these shares

Another option would be to use sharedup from a Windows client
It allows you to dump the list of shares of your old CIFS server into a file, then you remove the ones you dont need on the new server
and use that file as input to another sharedup to create the new shares on the new server

You can find sharedup.exe on the Tools & Apps CD
Its usage is described in the "Using EMC Utilities for the CIFS Environment"

Rainer and Sagle, thanks for all the information.

As for simply switching the CIFS domain, I did just that by backing up one step to dlete/remove the CIFS server in question. Only after this deletion could I then recreate in the new prefered/different domain.

The export mappings remain, so as long as the same name is used, the data is again accessible assuming you use the same name

Aside from the commands and scripts, I have used sharedup before, but failed to remember you can simply pump the reults to a text file a particular CIFS for just those desired results. Also, via Celerra manager on "CIFS", the CIFS shares tab you have the opton of viewing not only a particular DM but a just a file system as well. Since we have our file systems compliment each CIFS server in name, a quick view of shares attached to a particular CIFS in our environment is pretty easy.

Thanks again to all that assisted.

This is how I did Domain Migration

This Activity will be performed in following steps

• Schedule the activity
• Inform Requestor to Notify users about the activity
• Capture the current details of the CIFS server
• Capture the OLD OU and NEW OU
• Delete the CIFS server
• Create NEW CIFS server of same NAME adding new Domain
• Login to CLI using putty
• Join the Domain
• Take RDP to any wintel machine => START => RUN => Enter dsa.msc ( this will open Active Directory ) => Navigate to OU path
• Check the CIFS server should be reflecting with details as NAS Managed
• Check with Requestor to access the CIFS Server or Share of the CIFS server.