Jump to content

Domino

Mod Staff
  • Posts

    5,042
  • Joined

Everything posted by Domino

  1. Okay, so they're both currently global catalogs, which is good. But those options on DC1 means it's considered itself out of date, and stopped replication after being restored. If you're confident everything else is working properly, you can remove those options and see if it replicates properly with "repadmin /options -DISABLE_OUTBOUND_REPL" and "repadmin /options -DISABLE_INBOUND_REPL"
  2. It could just be that it's tombstoned itself due to the restore - If you run repadmin /options on the two DCs does DISABLE_OUTBOUND_REPL or DISABLE_INBOUND_REPL appear?
  3. You restored a DC? which one had the FSMO roles at the time? If you've a working domain controller in the domain I'd never recommend restoring another, there's too much chance of issues when it comes back : Domain Controller Recovery In all honesty, I'd say blow away the restored DC, remove it from AD using ADSIedit and then build a new server and DCpromo it.
  4. When I first moved to vanilla from a software managed solution, we used the MS 'common scenarios' package as a starting point. Download Group Policy Common Scenarios Using GPMC from Official Microsoft Download Center These give you a few seperate ways of locking machines down, which you can then customize to fit your needs. Still needs a lot of testing and work though.
  5. how much storage are they expecting to get out of it? I suppose two RAID1 groups with boot drives on the SSDs and data on the Large drives would be doable. Probably preferable to the file shares on a DC. However I'd be concerned about the expectations for the hardware given the limited resources
  6. Well you could script it with a foreach loop to run through one command, then the other? PowerShell Foreach Loop operator | Foreach-object cmdlet
  7. or add " -PassThru " onto the first command get-mailbox | Set-CasMailbox -OwaMailboxPolicy "Student OWA Policy" -ActiveSyncEnabled $false -PopEnabled $false -ImapEnabled $false -MAPIEnabled $false -PassThru | Set-Mailbox -AddressBookPolicy " Student Address Book Policy" http://windowsitpro.com/powershell/q-there-way-pipe-object-multiple-commands-when-using-powershell
  8. Run get-mailbox | Set-CasMailbox -OwaMailboxPolicy "Student OWA Policy" -ActiveSyncEnabled $false -PopEnabled $false -ImapEnabled $false -MAPIEnabled $false then get-mailbox | Set-Mailbox -AddressBookPolicy " Student Address Book Policy"
  9. Well 'get-mailbox' gets all the mailboxes, and passes that to 'set-casmailbox'. the output from 'set-casmailbox' is passed to 'set-mailbox'.
  10. Because the 'set-casmailbox' command doesn't return an output?
  11. on behalf of everyone...please don't change your sig to that monstrosity...
  12. 7/10 ...whoops
  13. @abillybob you're now being insulting in return. @Jasbo has already said he "wasn't dissing" - and I think you're taking a hypothetical as a personal attack As I said before, keep it civil please. I don't want to lock OPs thread when it's also prompted a useful discussion.
  14. Domino

    PSU Query

    Woah, dude that's deep.
  15. Guys, please keep things civil - we're all working towards the same goals here. @abillybob I'm sure it wasn't meant in the insulting tone you've taken it in, and @Jasbo Your point is valid, but explaining the possible issues is probably a better move. Back on topic: Your DC is the lifeblood of your domain, usually dealing with authentication, DNS, replication, addressing all at once. and also with more technologies getting AD aware and integrated it's becoming ever more vital. For a long time, the best practice wisdom has to keep DCs as only DCs wherever possible. Previously I've run DCs with secondary tasks/roles and not had any issues, but after some pretty terrible replication issues raising their head recently we're moving totally in the other direction and only running DC roles on them. TL : DR version is - it would probably be fine, but virtualbox attaches directly into the network stack, and your DC is useless without it. The chance for disaster increases in networks with multiple DCs, as any interruption to the synch processes is awful. In this position myself now, I would suggest doing as @pantscat said, and making the physical server a host for multiple VMs. Make sense?
  16. one like this?
  17. #ohgodtheformatting
  18. Domino

    New i7 PC

    The difference between the high end i7 and the high end i5 is hyperthreading. Which you'll not be using.
  19. That same section of group policy, you want the Set the intranet update service for detecting updates: Set the intranet statistics server: keys set to "http://mywsusserver.mydomain.whatever" If you're gonna do automatic installs (probably best to be fair, with the rate security patches are happening) you'll want to do them out of hours. Also, I'd suggest ensuring your servers are under another policy...
  20. Got the 'Specify intranet Microsoft update service location' section set there too? also, 2PM - that seems ill advised? [EDIT] - whoops, missed you were just doing a download
  21. Run "gpupdate /force" on a client?
  22. Added your GPO to point clients at the WSUS box?
  23. So, when're you installing?
  24. Anker is the way to go man, lots of good reviews across the board. ..and I know lots of edugeeks are happy customers too.
  25. @Dos_Box just got home....annnnnnd, relax
×
×
  • Create New...