- TsooRad is a blog for John Weber. John is a Skype for Business MVP (2015-2016) - before that, a Lync Server MVP (2010-2014). My day job is titled "Technical Lead, MS UC" - I work with an awesome group of people at CDW, LLC. I’ve been at this gig in one fashion or another since 1988 - starting with desktops (remember Z-248’s?) and now I am in Portland, Oregon. I focus on collaboration and infrastructure. This means Exchange of all flavors, Skype, LCS/OCS/Lync, Windows, business process, and learning new stuff. I have a variety of interests - some of which may rear their ugly head in this forum. I have a variety of certifications dating back to Novell CNE and working up through the Microsoft MCP stack to MCITP multiple times. FWIW, I am on my third career - ex-USMC, retired US Army. I have a fancy MBA. One of these days, I intend to start teaching. The opinions expressed on this blog are mine and mine alone.
When you are in front of clients in the pre-sales mode, you need good, solid information that you can relate. And the information needs to come from reliable, quotable resources. This article on Forbes.com presents an initial analysis of a new McKinsey report on collaboration. I encourage you to track down the actual report so you dig out the nuggets that will help you be more successful. There is nothing in this particular article that is vendor specific; rather, the information is business related and gives quantifiable data points using common metrics. Perfect for creating credibility and focusing the discussion on business requirements and pain points.
Part of being a consultant in knowing what needs doing and what does not need doing – and this is per project. However, there is always the starting, generic list. What follows is an example of that list. The elements of this list represent those subject areas that need attention at some point in the Lync project. Each of these elements has between three and 10 more sub-elements. In some cases, the sub-elements have tertiary elements. If a task needs to be at the quaternary level, I consider it for a move or maybe that I need to move its’ parent up a level. This avoids the issue of having too many project levels and getting lost in the weeds during planning; or worse yet, overlooking a project task. Remember that not all of these will apply to each project you do. And this list can be easily modified to meet core Exchange projects also.
1. Conduct Requirements discover
2. Design Lync 2010 Server System
3. Specify Client Deployment
4. Build Host Servers
5. Train the Trainer
6. Install SQL 2008 as two-node cluster
7. Install and configure 2 Lync EE FE servers as pool
8. Migrate existing R2 pool and users and component functionality
9. Remove existing R2 system
10. Install and configure HLB devices
11. Install and configure Monitoring and Archiving Lync Server roles using VM
12. Create Hyper-V specifications
13. Modify DNS
14. Modify External DNS
15. Assist with Certificates (External)
16. Assist with Internal PKI
17. Firewall rules
18. Configure ISA/TMG RP
19. Install and Configure Lync Edge Server pool
20. Define IP (internal and external)
21. Install and configure media gateway
22. Assist with Avaya PBX changes
23. Install, configure, & test Exchange UM
24. Create Dial Plan
25. Implement Dial Plan
26. Project Management
Just in case you cannot find these docs elsewhere (and also so I don’t forget myself) – here are a few links to Lync Server documentation:
The Port Change Issue On a project where the SQL team has a policy of changing the SQL port away from the default of 1433? This does not po...
Have you looked at the Lync Server/Skype for Business Server Open Interoperability Program (OIP) and wondered who some of the qualified pr...
Do you need to test outbound calling to international numbers but your customer doesn’t have anyone just sitting there waiting for your call...
AudioCodes has a new phone, the 450HD – complete with a touch color screen. I have been using the 450HD as my desk handset now for a few wee...