@IRJ said:

@alexntg said:

@IRJ said:

@alexntg said:

You had my curiosity piqued, so I went ahead and upgraded my test SW system to 7.2. I didn't notice anything major different from 7.1 for the helpdesk. It still has the same feel. For a basic internal helpdesk, it does the trick.

Yeah, but 6 and 7 are much different. I havent used 7 in production. I was just curious.

Yes, that difference is quite significant.

Which one do you prefer?

Seven. It's quick, clean, and simple. I want to jump in and work on tickets, not deal with endless categorization and taxonomy. If I were approaching tickets from a metrics perspective, it takes a couple clicks to get to the more detailed features, so that may not be a good fit in that case.

@IT-ADMIN said:

@Dashrender said:

@Dashrender said:

what server is providing DHCP for the branch PCs?

Again, what server is providing DHCP to the branch PCs? Is the scope set correctly to give the PC's the DNS of the branch DNS server.

yes, the DHCP is providing the correct DNS setting which is the ip of my ADC as primary DNS and the internet gateway as secondary DNS

For the branch site, the DC should be primary DNS, and the DC at your main location should be secondary. Non-AD DNS sources should not be used.

@IRJ said:

@alexntg said:

You had my curiosity piqued, so I went ahead and upgraded my test SW system to 7.2. I didn't notice anything major different from 7.1 for the helpdesk. It still has the same feel. For a basic internal helpdesk, it does the trick.

Yeah, but 6 and 7 are much different. I havent used 7 in production. I was just curious.

Yes, that difference is quite significant.

@IT-ADMIN said:

@alexntg said:

@IT-ADMIN said:

@scottalanmiller

when i run nslookup in any branch computer, it resolve successfully but it use the main DNS even if i they have as primary DNS the ADC ip address
what anger me is that machines in the branch office neglect the ADC

What happens when you force nslookup to use the branch server?

really i didn't try that, but tomorrow i will go to the branch office and try this, thank you

You can try it from your computer, even. Just force nslookup to use the branch DC.

You had my curiosity piqued, so I went ahead and upgraded my test SW system to 7.2. I didn't notice anything major different from 7.1 for the helpdesk. It still has the same feel. For a basic internal helpdesk, it does the trick.

@IRJ said:

@alexntg said:

@IRJ said:

@alexntg said:

So you're still working on a company name? Atlantic Tech's already in use: http://www.atlantictechnology.com - when you're creating a company, come up with something unique. That way, you can avoid trademark/IP infringement issues down the road.

The sell entertainment systems and you can see that right away when you go to their website. Finding a unique name is tough.

IRJ Tech? IRJ Systems? irj.biz is available. IRJ Enterprises? irj.enterprises is available.

IRJ stands for Indian River Joel. While that is great for a fishing business. Not so much for a tech business.

Oh, I thought it was a personal branding.

@ITcrackerjack said:

@scottalanmiller Correct, that's just for DBA Sole Proprietors. Do you usually recommend LLCs? In CA, the cost to register an LLC seems kinda steep for a consultant starting out. I agree it's a good (great) idea, but many don't due to the cost. I'd like to hear your reasons (though I'm sure I can guess most of them).

In 2012, I started my own consulting firm as a sole proprietor, but it wasn't profitable. After I shut it down, I was still held responsible for the (albeit minor) debt the company still had.

@IT-ADMIN said:

@scottalanmiller

when i run nslookup in any branch computer, it resolve successfully but it use the main DNS even if i they have as primary DNS the ADC ip address
what anger me is that machines in the branch office neglect the ADC

What happens when you force nslookup to use the branch server?

@IRJ said:

@alexntg said:

So you're still working on a company name? Atlantic Tech's already in use: http://www.atlantictechnology.com - when you're creating a company, come up with something unique. That way, you can avoid trademark/IP infringement issues down the road.

The sell entertainment systems and you can see that right away when you go to their website. Finding a unique name is tough.

IRJ Tech? IRJ Systems? irj.biz is available. IRJ Enterprises? irj.enterprises is available.

@IT-ADMIN said:

@alexntg said:

@IT-ADMIN said:

@alexntg said:

Ok, and what is the primary DNS on each client set to?

i set client in the main office to use the main DC for DNS resolving and set branch client to use branch DC for DNS resolving

And if you run an nslookup against the branch DC, does it resolve queries?

nslookup in branch client machine or branch DC itself ??

Nslookup from any client computer, and specify the branch DC as the DNS server.

@Dashrender said:

How many mailboxes? Are they moving to O365 or another inhouse Exchange server?

$9K could be a pretty good price depending on so many factors.

Right! It could also be way lowball. Being medical, there's encryption and DLP requirements to contend with, as well as message retention and granular message recovery. Also, if it's a 100-person hospital, or 20,000, not to mention if the contractor's doing the actual move, or if they're just doing setup and basic training.

@IT-ADMIN said:

@alexntg said:

Ok, and what is the primary DNS on each client set to?

i set client in the main office to use the main DC for DNS resolving and set branch client to use branch DC for DNS resolving

And if you run an nslookup against the branch DC, does it resolve queries?

So you're still working on a company name? Atlantic Tech's already in use: http://www.atlantictechnology.com - when you're creating a company, come up with something unique. That way, you can avoid trademark/IP infringement issues down the road.

@IT-ADMIN said:

@alexntg said:

@IT-ADMIN said:

what about the replication that take place in time, it seems that the branch DC don't respect the Active Directory Sites and Services at all, because i configure the replication to take place at night and finish in the morning

and how to force branch machines to login from their local DC, ???

The default replication schedule of a couple hours should be sufficient for most needs. Any more than that could leave the two sites rather out of sync. Less than that's a waste of bandwidth.

but at lease the branch DC should respect the schedule, \

Is their local DC a GC as well?

Yes it is both a global catalog and DNS server

Ok, and what is the primary DNS on each client set to?

Tek was bugging me, but I couldn't recall why. Found it!

http://en.wikipedia.org/wiki/TekWar

@IT-ADMIN said:

what about the replication that take place in time, it seems that the branch DC don't respect the Active Directory Sites and Services at all, because i configure the replication to take place at night and finish in the morning

and how to force branch machines to login from their local DC, ???

The default replication schedule of a couple hours should be sufficient for most needs. Any more than that could leave the two sites rather out of sync. Less than that's a waste of bandwidth.

Is their local DC a GC as well?

@IRJ said:

How do you feel about spelling Tech as Tek in the business name? I was thinking of a business name using tech but all domains are taken. I found that using the business name with tek in it it, shows an available .com domain.

That is really personal preference. There are popular sites out there, such as tek-tips.com, but to me it ranks up there with textspeak in a negative fashion. irjtech.com is available.

@scottalanmiller said:

@Dashrender said:

@alexntg said:

.net domains were for ISPs and networking providers, so depending on your business, they may or may not be a good choice. There's always the country-specific TLDs, such as .us.

That used to be the case, but certainly isn't any more.
My office went with a .net for email (I have no idea why - I wasn't around when that decision was made).

Still is the case. Just widely abused. It you use a .net inappropriately it reflects poorly on the company - makes the look confused.

Much like this is an Italian website.

@Dashrender said:

Assuming the links between locations can handle it, I'd have the another server pointing at this one. As for knowing if there are problems, the local clients will be using the DNS of the local server, in the case of the OP, both servers DNS server will be being used by clients. If there are problems you should find out through complaints from them.

The clients should be set up to use a second DNS server at a different site. If the first one is unavailable, the clients wouldn't notice.

@Dashrender said:

@alexntg said:

A few things:

1. Each DC should only point to itself for DNS. After turning a member server into a DC, you may need to adjust its DNS settings accordingly.

I'll go on the record and say I disagree with this. At minimum every DC should have a secondary IP of another DNS server (assuming you have at least two). Furthermore I typically set my DC's to point to the other DNS server for the primary and itself as the secondary. This allows ADDS to have an active DNS source while booting since local DNS might not be completely up before ADDS starts (if this has been resolved on 2012 I might be a bit behind these days).

It's a bit of a catch 22. There have been a few times that I've had to put a second DNS server in due to boot hanging. The flip side is that if you have a 2nd DNS server in and its own DNS server fails, how would you know to correct it? You may not notice the issue until the other DNS fails.