@IT-ADMIN said:

i know that the best practice is to have one additional DC in the branch office, but unfortunately i still not have the skills to get that done, this project was not successful and i risked to damage the main DC because it seem that there was some kind of conflict between the 2 DC, now i'm thinking about having child DC in the branch office, this is my next plan, hoping that will be successful

best regard

Do you mean a child domain? There's very little reason to use a child domain unless there's a legal separation requirement between two business entities or you have so many computers that a single domain wouldn't be practical.

@Dashrender said:

@alexntg said:

put the computers that will be accessing it under SA (recurring annual), which would also grant them Windows 8 Enterprise.

I don't think this is correct any more. I think you have to have a Windows 8.1 Enterprise Open License added to your base Windows 8 license regardless of SA to get Business edition now (recent change)

I'm pulling info from here: http://www.microsoft.com/licensing/about-licensing/briefs/win8-virtual.aspx - If you have something more recent, I'm all ears.

@IRJ said:

I see where what you are saying, but the chances of that scenario are slim to none. If there was a cataclysmic event that took down the main branch completely, the likelihood of them building the infrastructure at the second branch from the ground up is highly unlikely.

If they are backing up offsite, they would be more likely to restore everything to the original site or the cloud. The likelihood of them buying equipment in a small branch office and rehosting everything there is almost non-existent. I doubt they have the space to build a datacenter.

Recovery and full restoration are different processes. For Recovery, enough VM hosts to cover the basics and a some switches would cover it. It doesn't need to be pretty or perfect. You wouldn't need a whole datacenter.

@IRJ said:

@alexntg said:

@IRJ said:

@alexntg said:

@IRJ said:

@scottalanmiller said:

You might want to consider a second DC at the main site.

I recommended that a week ago. Its alot easier to manage.

Having a second DC at a main site without one at a remote site doesn't really offer any advantages. If the site fails, you're out both DCs. If they're spit one at each site and the clients are pointed properly, the setup could suffer a WAN link failure without losing authentication, and one of the DCs could fail without any major issue. The only time there would be an issue is that if the WAN's down and one DC's out, but one of the sites would still continue to work properly.

From my understanding, All the resources are at the main site anyway. So what good is authentication, if there are no resources that need to be authenticated?

Disaster Recovery's a good start. If the main site's unavailable, you can use the offsite DC as a start for recovery. Also, if considering WPA Enterprise, having a local DC/RADIUS would be useful. Otherwise, a loss of WAN could result in loss of WiFi.

I dont understand what you mean by using the offsite DC for recovery. What are you going to recover from a DC? He will probably continue to make changes from the Main site DC and replicate them to the offsite DC.

For DR, there's no more main site to make changes at. The secondary site then becomes the primary site. There'll be a need to hook up some more computers to handle the overflow staff (assuming any staff survive the event). Having a DC available would be most useful, and it would serve for authentication to any servers you stand up at the second site during recovery. If the infrastructure's in place at the second site, there's no reason to not have a DC there. For the amount of computers, there's no workload need for 2 DCs at any one site.

@IRJ said:

@alexntg said:

@IRJ said:

@scottalanmiller said:

You might want to consider a second DC at the main site.

I recommended that a week ago. Its alot easier to manage.

Having a second DC at a main site without one at a remote site doesn't really offer any advantages. If the site fails, you're out both DCs. If they're spit one at each site and the clients are pointed properly, the setup could suffer a WAN link failure without losing authentication, and one of the DCs could fail without any major issue. The only time there would be an issue is that if the WAN's down and one DC's out, but one of the sites would still continue to work properly.

From my understanding, All the resources are at the main site anyway. So what good is authentication, if there are no resources that need to be authenticated?

Disaster Recovery's a good start. If the main site's unavailable, you can use the offsite DC as a start for recovery. Also, if considering WPA Enterprise, having a local DC/RADIUS would be useful. Otherwise, a loss of WAN could result in loss of WiFi.

@IRJ said:

@scottalanmiller said:

You might want to consider a second DC at the main site.

I recommended that a week ago. Its alot easier to manage.

Having a second DC at a main site without one at a remote site doesn't really offer any advantages. If the site fails, you're out both DCs. If they're spit one at each site and the clients are pointed properly, the setup could suffer a WAN link failure without losing authentication, and one of the DCs could fail without any major issue. The only time there would be an issue is that if the WAN's down and one DC's out, but one of the sites would still continue to work properly.

@Minion-Queen said:

What we will be needing is someone to do quick drive swaps and server hookups (smart hands) no actual technical work needed.

That sounds like a job for Onforce.

@scottalanmiller said:

You might want to consider a second DC at the main site.

Or just fixing the one at the remote site.

I sense a resemblance here:

Go into your settings and reset your autocorrect. As you type, train your autocorrect. You'll have better luck, and it'll learn words that you use regularly that aren't in its dictionary. It'll be a little slow-going at first, but once it learns your typing, it's fantastic. I have 4 years of autocorrect data for my iPad, and it's pretty fluid, even for IT acronyms.

@scottalanmiller said:

Nope. Have never done any training.

So if you're typing and it starts to autocorrect, you never tap the popup to cancel it?

@NetworkNerd said:

I'm about to create a VM for our Estimating department to use to access a particular software. The company only wanted to get one seat, and as most know, a single seat tied to a specific computer is cheaper than network licensing most of the time. Basically this VM will run Windows 7 / 8.1 and allow one user at a time to login and use the program via RDP. We don't use VDI in any way. Other than the fact that this will be a VM, it is literally no different than having a desktop computer that is always online.

My CDW rep is telling me I need a license of Windows 8.1 Enterprise rather than Pro so I can leverage the VDA usage rights. I thought I just needed a license of 8.1 Pro (open license, not retail) to cover the requirements here. Can someone straighten this out for me?

Correct. You'll either need to pick up a VDA license (recurring annual) for the desktop VM instance or put the computers that will be accessing it under SA (recurring annual), which would also grant them Windows 8 Enterprise. Otherwise, running a Windows desktop OS in a virtual environment would be out of licensing compliance.

Ah, a development company. That's far outside my realm of experience, sorry.

@Vladimir-Eremin said:

A small trick regarding usage of configuration backup.

If you have a network share, you can create a share disk, map it to instance of VB&R and use as a target repository for configuration backup. Should any disaster situation happen (VB&R server goes down, for instance), all you would need to do is to install Veeam on any other virtual/physcial machine and import previously backed up configuration.

Thanks.

Or, if you have the free space available, make a replica of your Veeam server and a domain controller, then put them in the same location as your backup.

What software solutions would you be working with?

I replied to your other post earlier this morning:
http://community.spiceworks.com/topic/post/3353674

@JaredBusch said:

Ok, wow. I love the mechanics.. It will definitely let you see player skill.

Exactly! That's why I like the game. Combat's immersive and you really find yourself getting into it instead of standing there hitting the 3 key all day. Standing there and having a slugfest with your target will get you killed (which I learned the hard way). Player skill is important, and the classes are diverse enough that there's something for every play style.

Interesting. My iPad accepts gave. Is this a fresh iOS install, or have you been training autocorrect?

Do you have a Win2008 R2 machine available? I haven't tried it, but it an 7 are on a similar platform.

@scottalanmiller said:

Really? I'm older than you and we weren't taught metric is school really (what is there to know?) but there was no concept that metric was ever coming down the pike nor have I heard anything to suggest that anyone is leaning that way since. I feel like metric has been even more eschewed in the years since then.

That's because you're older than me, and the movement likely started after you. If you were younger than me and noticed the same thing, there would be a problem.