Good point. Personally, I don't see a value for a comma or a space in this section. Some apps might though (they tend to be very old apps).
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Brad Sent: Friday, October 21, 2005 9:58 AM To: [email protected] Subject: RE: [ActiveDir] Interesting Scripting Task..... There is bound to be a way round, possibly to escape the character in question, in this case, the evil comma. I say it is bad practise but really I mean it isn't something I would want as opposed to the problems it can create (like this one). It comes down to a trade off between the "bit more work" and how beneficial/satisfying having a comma there is. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Al Mulnick Sent: 21 October 2005 14:40 To: [email protected] Subject: RE: [ActiveDir] Interesting Scripting Task..... Last I checked, it's not a bad practice to use commas. It's a bit more work to use the names if you have to escape the commas, but it's not a best practice. In fact, in a displayname, I do want to use commas, but I think you meant in the CN you wouldn't want a comma. I frequently do want them, but mostly because I've always worked with Exchange and the upgrade from 5.5 will often cause that. It's valid, it's not against any best practices, but it can be a pain to work with. You found a workaround, but I wonder if there's another way to handle the special characters? Just curious mostly. >From: "Smith, Brad" <[EMAIL PROTECTED]> >Reply-To: [email protected] >To: [email protected] >Subject: RE: [ActiveDir] Interesting Scripting Task..... >Date: Thu, 20 Oct 2005 15:16:59 +0100 > >All, Just thought a quick update might save a bit of pain for those of >you that ever want to use the CreateXMLFromEnvironment.wsf and >CreateEnvironmentFromXML.wsf scripts from GPMC. I found a snag where >CreateEnvironmentFromXML.wsf can't import user accounts where the name >contains a comma (and probably othe special characters). I know it is >bad practice to use these in display names, but it is supported by >dsa.msc and so inevitably has been used. There are a few ways around >this, I got past it by changing line 596 from > >szName = User.Get("name"); > >To > >szName = User.Get("samAccountName"); > > >This could be done a lot smarter I know, but for a quick fix this works >and is all I need for now. > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Smith, Brad >Sent: 12 October 2005 13:16 >To: [email protected] >Subject: RE: [ActiveDir] Interesting Scripting Task..... > >The script Darren pointed out seem to be working just fine, now I need >to configure a decent migtable ;-) > >Thanks again for the heads up Darren. > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Darren >Mar-Elia >Sent: 10 October 2005 17:40 >To: [email protected] >Subject: RE: [ActiveDir] Interesting Scripting Task..... > >Yes, Microsoft has attempted it. Check out the scripts directory under >the GPMC install. It has two scripts: > >CreateXMLFromEnvironment.wsf and >CreateEnvironmentFromXML.wsf > >That do pretty much everything that you've described below. > >Darren > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Smith, Brad >Sent: Monday, October 10, 2005 8:08 AM >To: [email protected] >Subject: [ActiveDir] Interesting Scripting Task..... > >All, > >I am pondering the possibility of automating the creation of >development environments. The problem I am hoping to solve is that a >lot of our testing needs to be done in an environment where all our >Ous, GPOs, Groups and so forth are present. Recreating this is a >nightmare, so to alleviate this I want to write an import/export >script that dumps all the OU's, Groups, Users and GPO's (including >security) and then restores them in a different target domain >(different forest too). Has anyone attempted/achieved this before? > >Brad > > >This email and any attached files are confidential and copyright >protected. If you are not the addressee, any dissemination of this >communication is strictly prohibited. Unless otherwise expressly agreed >in writing, nothing stated in this communication shall be legally binding. >List info : http://www.activedir.org/List.aspx >List FAQ : http://www.activedir.org/ListFAQ.aspx >List archive: >http://www.mail-archive.com/activedir%40mail.activedir.org/ >List info : http://www.activedir.org/List.aspx >List FAQ : http://www.activedir.org/ListFAQ.aspx >List archive: >http://www.mail-archive.com/activedir%40mail.activedir.org/ > > >This message has been scanned for viruses by MailControl - (see >http://bluepages.wsatkins.co.uk/?4318150) >List info : http://www.activedir.org/List.aspx >List FAQ : http://www.activedir.org/ListFAQ.aspx >List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ >List info : http://www.activedir.org/List.aspx >List FAQ : http://www.activedir.org/ListFAQ.aspx >List archive: >http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
