Skip to main content

Office 365 decision

Well, in the end we decided to hold off on the Office 365 decision, at my recommendation.  It really came down to what was best for the company right now.

There are important lessons here:

  1. Do your due diligence, investigate the options, speak to multiple vendors - you will learn something, and might even be able to save the company some serious money
  2. If you don't have the time to do one migration, don't try and do three at once
  3. As an admin, you only see a small part of the picture - get everyone (all stakeholders, as they say) involved IN PERSON
  4. MS Project - get all PM stakeholders involved IN PERSON to decide what the company really needs - there are other (and much cheaper) alternatives
  5. If you don't have the budget for a migration tool, you should revisit the impetus to migrate
Regarding the last point - no, you don't NEED a migration tool.  Here's another list:
  • If you don't have the budget - will you ever?  Are you trying to rush without some sort of migration aid?
  • Have you ever successfully completed a migration of this scale with these exact products before?
  • What is your back-out plan?
  • How much time do you have invested in user training?
  • Do you even have a project plan?
Of course, if you have sub-50 users, this probably doesn't apply...maybe even sub-100 users.  But from my experience as soon as you get out of the 25-50 user range things start to become 'serious business'.  If you don't have the time to do this correctly and properly, you should reconsider the decision.  If you can plan and train properly but are crunched for time - you NEED a migration tool.  The benefits to management should be fairly clear - zero to very little service impact, greatly reduced time to migrate, and most tools come with professional support.

Good times...migrations are, in my experience, the most involving of IT admin tasks mainly because it requires so much person-to-person interaction (whatever that is) and meetings.  Whee.


Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:

You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):

If you use a user object to auth (such as a service account, or admin account):

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/ is registered on these accounts:
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get here's a config and brain dump...

You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…