@Jason said:

All built in admins on domain are renamed to random names. And the local administrator is deleted with a new one created with a random name (this is so the SID will not be the same)

Do you do this via GPO? If so any kb or technet link for this? I am sure I can find this within couple minutes of googling, but the more the better.

Here's the changes:
Built-in Administrator : Change password.
I created a new account with @brianlittlejohn suggestion and made it domain admin.
Same with the new manager.

Thanks

As a sole admin, I have no problem using built-in administrator to remote into each server. Next month I will have one more administrator joining. However, his role will be IT Manager, oversee me and web/app designer.
With that said... what is a recommended best practices when there are multiple administrator? Do I add him into Administrators group and be done with it?

@brianlittlejohn said:

@Dashrender said:

@LAH3385 said:

(all hypervisor are licensed).

What does this mean? Hyper-V is free, so there is no license.

I'm assuming he means he has the windows licenses necessary for every node in his cluster.

YES! that is what I meant to mean.... I mean... I meant... whatever.. English....¯\(ツ)/¯

@brianlittlejohn
Such as? I would create a checkpoint before I leave for the day, and remove checkpoints over 2 weeks old. Bad practice?

@brianlittlejohn said:

@LAH3385 Only reason I can think would be if something happened to that DC VM itself.

But wouldn't that also be replicate to the other DCs as well? Unless you mean BSOD. As for BSOD, I think checkpoints would be best to correct it. Any suggestion in scenario for BSOD?

As the topic said... if we only have one location, do I still need multiple Domain Controller replications?
We used to have 2x 2008 R2 servers act as domain controllers. They are set up to replicate each other (except DHCP). Now that we upgrade to 2012 R2 with Hyper-V failover cluster... do we still need multiple Domain Controller like before? We could potentially have 4 nodes capable of moving DC around (all hypervisor are licensed).

Maybe this question should be direct to our Accounting department

We have Veeam Endpoint 1.1.2.119. How do we upgrade it to 1.5? Reinstall? Will that break the backup sequence?

Our company has been using CDW, SHI, PCM, etc for all our equipment for the past years. Now that I am in charge of researching for pricing, We have to work around budget so I cannot go spending spree on these. I usually goes for Newegg, Amazon, etc as they are easier for me. Especially Newegg is a Free Shipping (premier account) + Tax is not applicable in our state.

So do you account for tax when buying equipment? Say... Monitors. Why? Why not?

@Jason said:

Most likely something is wrong with your customizations on the MSI you are deploying.

If that is true, then after reno uninstaller > install via installer should fix the problem.
unless the .msi of the installer itself is the cause. I used .exe for manual install.

@gjacobse said:

Something doesn't seem right - as you have eluded to.

Manually uninstall Adobe then run CCleaner to clean the registry. After that, manually install the Adobe.

That is a good idea.

I install this copy of Adobe Acrobat XI via GPO publish. Somehow after the installation it is missing PDF icons.
Before this acrobat, this PC was installed with Adobe Reader DC (ninite). The user wants Acrobat, so I uninstall Reader DC, then intall Adobe Acrobat via publish. Now it is missing pdf icon.

Another machine I tested with I install via publish GPO with no prior Adobe installed, and did not ran into missing icon issue. Maybe because Reader DC is not compatible with Acrobat?

Step taken:
Manually uninstall > restart > reinstall via publish = missing icon
RenoUninstall > Restart > Restart again > reinstall via publish = missing icon
Reno Uninstall > Restart > Restart > reinstall via installer = missing icon
Uninstall with AdoAcrobatCleaner > Restart > reinstall via installer = missing icon.

I don't know what to do next. The application works even without icon, but it looks weird. Please help ** cry in tears of defeat **

EDIT: Answer

One time I receive a package at 8pm from a sedan car.. who clearly not a USPS vehicle. Just be patient.

@dafyre
Define.. something special..
link to this post I am configuring new DHCP server to change the DHCP server itself and subnet mask. The old DHCP server has other options aside from the listed 3 above.
004 Time Server
005 Name Server
044 WINS/NBNS Servers
184 NCP

My current DHCP server is OLD and maybe outdated. I want to know if there is any best practice for Scope Options. So far I have:
003 Router 192.168.1.10 (gateway for firewall router)
006 DNS Servers 192.168.1.23, 192.168.1.25, 127.0.0.1
015 DNS Domain Name costro.com

I know there are more options I should consider of, but wonder which do you recommended?

I see.. Gotta play by their rules.

@JaredBusch
To make it simpler for me. Would /22 starting at 192.168.1.1 to 192.168.4.254 better than 192.168.0.1 to 192.168.3.254?

@coliver said:

Am I reading that right that you want to to exclude the entire 192.168.0.1/24 subnet?

For the time being. yes. It will be open to public later. I don't have a solid game plan yet so might as well keep everything the way it is (starting at .1.xx)

@JaredBusch said:

This is easy, you just have to plan it out. Note, you cannot "change" the scope of your DHCP server. You can choose to add another or wipe it and reimport it via PowerShell (what I typically do).

1. Understand what your new range will be. Since you are on X.X.1.X/24. the new scope will be X.X.0.X/23.
2. Update your router LAN IP to use the /23. If it was X.X.1.1/24, it is now X.X.1.1/23.
3. Update your DC (asusming a WIndows network here) to use the new /23.
4. Put a test device manually on X.X.0.X/23 and make sure you have internet and can ping the DC.
5. Update all of your static devices to the /23.
6. Export the DHCP Scope via PowerShell Export-DhcpServer -ComputerName dhcpserver.contoso.com -File C:\exportdir\dhcpexport.xml
7. Edit the XML file to expand the scope. Here is an example of one I did this on a couple years ago. Basically change the ScopeID, SubnetMask, StartRange, and add an ExclusionRange for the entire X.X.0.1-X.X.0.255 initially. You can delete this exclusion in the GUI later when you are ready to use it.
   
8. Delete your current DHCP scope from the GUI.
9. Import the updated scope from PowerShell. Import-DhcpServer -ComputerName dhcpserver.contoso.com -File C:\exports\dhcpexport.xml.
10. Refresh the GUI, enable the scope, restart the service, etc.
11. Make sure all the settings migrated in correctly.
12. Force a machine to DHCP renew and you are done.

Does this looks about right? 1.1-1.30 belong to current static IP addresses

When will you need IPV6?