Ken Schaefer <[EMAIL PROTECTED]> wrote on 09/18/2008 11:17:47 PM: > Please note the following issue from 2002: > http://support.microsoft.com/?id=319182 > > IE will not accept cookies from servers with invalid host names (e. > g. they contain an underscore). So, you can use these names in the > DNS, but if you are running a webserver at that address, you may > have issues with your browser (if it?s IE)
They're not, as it happens (these are legacy fileservers; when they come due for replacement, the new replacements follow our (now) naming convention, which has no underscores). Thanks for the link, tho. > > Cheers > Ken > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, 19 September 2008 5:28 AM > To: NT System Admin Issues > Subject: Re: new computers > > > "Jonathan Link" <[EMAIL PROTECTED]> wrote on 09/18/2008 03:25:05 PM: > > > DNS lookups. Underscores are not valid in DNS names. > > But they will work .. > > Z:\>nslookup admin_nt9 > Server: admnwdc001.wrk.ads.pha.phila.gov > Address: 10.64.7.53 > > Name: admin_nt9.wrk.ads.pha.phila.gov > Address: 10.64.13.3 > > > In Win2000 AD. This is internal only, of course. > > > > > On Thu, Sep 18, 2008 at 3:09 PM, Joe Heaton <[EMAIL PROTECTED]> wrote: > > Second question. Anyone know what could break using underscores in PC > > naming? i.e. loc_pcname > > > > Joe Heaton > > > > -----Original Message----- > > From: Phil Brutsche [mailto:[EMAIL PROTECTED] > > Sent: Thursday, September 18, 2008 11:45 AM > > To: NT System Admin Issues > > Subject: Re: new computers > > > > I've done it both ways. I usually try to have the AD objects created > > first. > > > > If you create the AD object first the machine will get the right GPOs > > right off the bat. It's less work that way, especially if you use > > software installation GPOs. The machine is 100% ready to go sooner. > > > > Joe Heaton wrote: > > > When you guys build new PCs, do you create the AD object first, or > > > simply join the domain from the PC afterwards? I've always created > > the > > > PC, then joined the domain, but our desktop guy just mentioned that > > our > > > manager wanted him to create the AD object first. My first instinct > > is > > > to say no, because then you're creating an AD object for something > > that > > > doesn't exist yet, but other than that, I didn't have a real reason. > > > Anyone have a better reason? > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
