Jump to content

bshingler

Members
  • Posts

    57
  • Joined

  • Last visited

Reputation

40 Excellent

About bshingler

  1. yep ive tried that ages ago.. that restricts the default context menu on all file explorers however it does not stop the right click on the menu icon at the bottom (taskbar start button)..
  2. yep, imported the group polices already... there's no mention for it in the win10 reference startmenu
  3. hmm that doesnt exist in my group policies, that looks more like an XP config
  4. Has any one been able to remove right click on the start menu? ive tried turning off context menus on the start menu + task bar to no avail? is this possible or not ive disabled all the control panel options so its not a biggy just annoying.
  5. Asset disposal policy, security investigations policy, AUP
  6. how many clients are connecting to per AP? if over 30 your going to start seeing issues? are you on gig connections
  7. have you allowed local 127.0.0.1 to bypass the proxy?
  8. check what your filtering is doing and firewall ports
  9. no need datacenter just buy two licenses for server 2012 r2 and your good with will cover your server 1 on another note mate go have a look at microsoftvirtualacademy.com and virtualisation will probably explain alot for you and give you a better understanding of that can be achived.
  10. you can install wsus and wds on on your DC if you want? i like to keep things as simple incase disaster strikes - but then again loosing wds or wds isnt a big deal to be fair. Key here is your server 1 - decent cpu / mem and raid
  11. As a note virtual domain controllers should also be set in hyperv as do not save state - always shutdown
  12. Generally speaking should be joined into domain and will give you flexability if you then want to move to clustered setup as that needs to be in the domain.. You need an additional server running dc roles if you join into domain. Example you reboot hyperv server joined into domain.. Cannot find dc because your virtual dc hasn't started = a very long wait before you are able to login locally to start services nightmare.. Ms recommended practice is to have at least 1 domain controller separate to your hyper v server I would always recommend this server setup wise 1 domain controller = dc01 1 hyper v host = host01 1 backup server = Dpm / veeame however usb or nas box will work
  13. Veeam is best installed on a seperate server with storage for backup then i think you deploy an agent onto the hyperv server (correct me if im wrong its been a while since ive used veeam)
×
×
  • Create New...