Azure IaaS assessments: sizing lift-and-shift honestly
Field notes on running an azure migration assessment before you commit to lift and shift sizing: measured load, right-sizing down, and what should stay put.
12 notes from 2017. Product names and recommendations reflect that year — not today's catalog. Current notes (2024–)
// 2017 · 12 posts · archive year page
Field notes on running an azure migration assessment before you commit to lift and shift sizing: measured load, right-sizing down, and what should stay put.
vSphere replication disaster recovery, field notes: honest RPO/RTO tiers, stretch vs re-IP, and the DR runbook that has to actually fail over.
Azure AD PTA reached general availability at Ignite. Our pass-through authentication vs ADFS decision tree for the multi-domain federation farms we operate.
Microsoft says Teams is replacing Skype for Business. What Ignite 2017 actually announced, what it means for SfB estates, and the migration math we run.
Why XenDesktop 7.15 LTSR is our standard Citrix VDI architecture for 10,000-user estates: MCS vs PVS, NetScaler HA, and profile strategy that holds.
Field notes on Active Directory forest consolidation: target forest design, trust topology, SID history, and ADMT migration phases from a real program.
A field-tested BitTitan MigrationWiz review vs native hybrid moves: which Office 365 migration tools win by scenario, with throughput and licensing math.
Field notes from the WannaCry weekend: MS17-010 patch management, SMBv1 eradication, and SCCM emergency deployment rings across a 700-server estate.
Lotus Notes to Office 365 migration field notes: NSF mail and calendar fidelity, Domino directory sync, coexistence, and triaging Notes applications.
Microsoft Teams vs Skype for Business in 2017: what Teams can and cannot do at GA, and what we tell clients running SfB 2015 estates to actually do.
Exchange hybrid configuration in the field: HCW quirks, autodiscover priority, why free/busy stops working, mail flow choices, and public folder access.
Field notes from a SharePoint 2010 to 2013 migration: database attach upgrade order, Test-SPContentDatabase triage, claims conversion, deferred site upgrades.