Reputation
Top tag
Next privilege 50 Rep.
Comment everywhere
Badges
10
Impact
~7k people reached

Jun
22
awarded  Popular Question
Aug
27
awarded  Excavator
Aug
27
awarded  Editor
Aug
27
revised CentOS 6.4 and Audio Conversion
Edit: missing colon in URL's
Aug
27
suggested approved edit on CentOS 6.4 and Audio Conversion
Sep
17
awarded  Popular Question
Mar
12
awarded  Supporter
Mar
12
comment aggregating multiple ISP connections
I'll look into this
Mar
12
comment aggregating multiple ISP connections
Looks good, investigating now.
Mar
12
comment aggregating multiple ISP connections
While sympathy is always much appreciated, that hasn't exactly moved me forwards ;)
Mar
12
asked aggregating multiple ISP connections
Jan
8
accepted Hyper-V Redundancy without Domain
Jan
8
comment Hyper-V Redundancy without Domain
@TomTom, ok, makes sense. Plan is direct 1:1 copy anyway. I like that article, by the way.
Jan
8
comment Hyper-V Redundancy without Domain
Also, I wonder how nasty the process of migrating non AD W2000 not R2 to 2012 will be. And how long it is likely to take.
Jan
8
comment Hyper-V Redundancy without Domain
@TomTom - can you expand on coupling physical servers 1:1 - do you mean some automated way, or just manage the two by hand ? If automated - is there "One Microsoft Way"(TM) to do this ?
Jan
8
comment Hyper-V Redundancy without Domain
@pauska - I see you and TomTom are not getting on - seriously, would you like to post an answer suggesting your proposal for handling the issue. I genuinely would like to hear suggestions from people
Jan
8
comment Hyper-V Redundancy without Domain
@TomTom, powershell - yep, looks a likely solution. Failover Cluster just looks like way too much expansion of Windows setup, for no real benefit.
Jan
8
comment Hyper-V Redundancy without Domain
@TomTom, re handle HA in client: That's gonna be a pain in the ... for a rag-tag collection of various Centos's and a couple of ubuntu's
Jan
8
awarded  Commentator
Jan
8
comment Hyper-V Redundancy without Domain
Not entirely sure I understand what you are saying here (certainly due to my lack of knowledge on windows systems - last time I was a sysadmin for domains was NT4!). Optopn 1 would have clones on each guest on each vm server, so standby guests could not spin up as their (static) ip's could clash.