Book Update

I posted some gibberish a few weeks ago about another book project.  Well, I'm getting close to wrapping it up, so I thought I'd go ahead and blabber about it in case anyone has anything they'd like to comment on or any topics they'd like to see included in it.

The book is titled: The AutoCAD Network Administrator's Bible - 2013 Edition

I know: Not very creative or clever.  However, this is not a typical dust-off and rehash book.  I've been painstakingly re-writing it from start to end.  Some of the major changes included in this book:

• AutoCAD 2013 network deployments
• Design Review 2013 deployments
• DWG TrueView 2013 deployments

In addition, I've updated the deployment vector scenarios and included much more detail for each...

• Deployments with System Center Configuration Manager 2007
• Deployments with System Center Configuration Manager 2012
• Deployments with Active Directory Group Policy
• Deployments with Microsoft Deployment Toolkit (MDT) 2012
• Deployments with VBScript, CMD / Batch script, and PowerShell

There's still the familiar topics, which have been updated for the current product versions as well...

• Troubleshooting Tips
• FlexLM License Server architecture and implementation considerations
• Software Deployment strategies
• Tools:  Sysinternals, XCACLS, REGINI, MSICUU, REG, etc.
• Client Performance Optimization

As I've said before, if you have any particular ideas or topics you'd like to see included, post a comment and let me know.  I'm getting close to finishing it, but I'd still hold off for a good suggestion.  I'm looking forward to wrapping this project up so I can focus on my family and day job more as Fall sneaks into Virginia.

Cheers!

Read More

Windows 8 on TechNet: Not so Great for TechEd folks

If you attended Microsft Tech-Ed North America 2012, in Orlando, Florida, you got a nice gift: A free, one-year subscription of TechNet Professional.  However, what you might not have realized is that there are quite a few "flavors" of TechNet Professional.  The one given out at Tech-Ed NA is "TechNet Professional (NFR)", or "not for resale".  This version, or "flavor" (my own term), doesn't allow access to the same downloads as many other "TechNet Professional" flavors.  For example...

Windows 8 and Windows 8 Enterprise is available for download to the following subscription levels:

TechNet for Action Pack
TechNet for Microsoft Competency Partners
TechNet for Microsoft Competency Partners (VL)
TechNet Plus Consumer Service Professional Pilot
TechNet Professional (Certified Partner)
TechNet Professional (NFR Bundle)
TechNet Professional (NFR FTE)
TechNet Professional (NFR MCT)
TechNet Professional (NFR MVP)
TechNet Professional (NFR)
TechNet Professional (Retail)
TechNet Professional (SA)
TechNet Professional (VL)
TechNet Professional with Media (Retail)
TechNet Professional with Media (VL)
TechNet Standard (Retail)
TechNet Standard (VL)

Windows 8 Pro is only available for download to the following subscription levels:

TechNet Professional (SA)
TechNet Professional (VL)
TechNet Professional with Media (VL)
TechNet Standard (VL)

The net result is that if you happen to be running Windows 7 Ultimate, and you'd like to try out the much-touted and improved "upgrade" for Windows 8, well, you can't.  Windows 7 Ultimate can only be "upgraded" to Windows 8 Professional, which is not available on your "NFR" subscription level.  So, your only options are:

• Do a full install of Windows 8 or Windows 8 Enterprise, and reinstall everything again
• Wait and buy the "Pro" version upgrade when it's available
• Upgrade your TechNet subscription level (for a nominal fee, of course)
• Stick with Windows 7 Ultimate

Bummer.

Read More

Another Book

So, I had posted something about trying out a "different" kind of book several months ago.  I ended up scrapping that idea because I'm not up for that challenge (nor do I really have the time).

I have decided however, that I will do a follow-up to the AutoCAD Network Administrator's Bible, based on AutoCAD 2013 but this time mix in System Center Configuration Manager 2012.  I'm still dipping my toes into ConfigMgr 2012, so it will be interesting to see where it leads.

I any case, I am open to suggestions for topics or examples to cover in this book.  If you have something you'd like me to include that relates to the planning, deployment and administration of Autodesk products in a network environment, drop me a line at ds0934 (at) gmail (dot) com, and be sure to use the subject line "Book Suggestion" so my spam filters don't kill it immediately.

Read More

Babies and Bath Water

You've probably heard that age-old phrase: "Don't toss out the baby with the bath water."  We've all heard it many times.  It's amazing how few people really let that sink in.  I was thinking about some of the projects I've been involved with over the past few years.  The key players.  The major issues.  The conflicts, challenges and resolutions at every milestone.  I also recalled the personalities and alliances and adversaries.  Then I remembered how many times a suggestion was discarded simply because it was bundled with a collection of issues, some of which were not ideal.  Rather than pick and choose, the entire bucket was sent back to the kitchen.  I still see this happen all the time.  The next time you're considering some idea for improvement, and maybe it was proposed by someone you don't particularly care for, or respect much, ask yourself if you really don't like the idea because of technical merit or because of who suggested it.  And then ask yourself if there are any pieces of it that might be of value, rather than wrapping the whole thing up and stamping it for rejection as a whole.

Read More

Prez-o-dent / schmez-o-dent

I've been working since before I graduated high school. That would be somewhere in the mid/late 1970's. My first paying job was back when Jimmy Carter was president and I'm still a long way from retirement. I've seen a lot of so-called "change" over that time, but I'm still confused by all the talk about how much impact a "new" president has on the American public. I hear a lot of fuss about it. TV ads, radio ads. Coffee room chatter.

Really?

Explain this please?

What impact does a US president really have?  Really.  I mean: seriously. Ok. So he can nominate a Supreme Court justice on occasion, but that's still not an appointment. The nomination has to be vetted and approved by others.

Then there's the talk about Executive Orders. But when you look over the EO history, it's really not that impressive or impactful. There's really nothing sexy there at all, and Executive Orders can be reversed.

So, I am still confused by the focus on how much impact a "new" president really has.

Can they control the economy?  No.
Can they control medical breakthroughs?  Not directly.
Can they control gasoline prices?  No.
Can they control who wins American Idol?  No.

I have to say, in all my years of working, I have never seen, or experienced any meaningful or significant "change" in my job, income, career opportunities, family life or social activities as a direct result of voting in a new president. Never. I didn't see any real change in my life under Carter, Reagan, Bush, Clinton, Bush Jr., or Obama. None. Zero. Zip. Nada. Nil. If you blindfolded me, put me in a time machine back to anywhere from 1976 until now, hid all the calendars, and asked me who the president is, I doubt I would know. Maybe by style and fashion, or tv shows I could guess, but certainly not by any meaningful criteria.

I have seen "change" as a result of overturn in Congress and Senate however. Oh yes. That I have seen. In fact, I have seen more "change" from local city elections than I ever have from a federal election.

Basically, in my humble view, the role of the US president is nothing more than a mouthpiece and figurehead. The news media has done a great job of programming the public into believing that the president can really invoke "change" without others involved.  It's like they have some magic wand, or magic crystal ring.  Sha-zam!  Instant Recession cure.  Instant job creation.  Instant insurance fix.  Instant Gitmo closure.  Instant terrorism fix.  Ho ho ho.  Keep wishing.

It's amazing. It's like we've forgotten everything we learned in elementary school. I shouldn't be surprised.

So. I ask you to do one thing: stop and think about each time you've experienced a change of presidential leadership in America, what exactly did you see "change" in your immediate life as a result? Not in the general public. Not on TV.  Not what your friends, neighbors, coworkers, and relatives blabbered about.  I  mean: in YOUR immediate life. And then, if you can even think of one thing, can you absolutely pin that on the president? Or was it really something that actually came from Congress or the Senate?

Each time I hear an ad that says "what will the first 100 days of a president (dipshit-asswipe) administration be like?" and they start off on listing all the "change" that will happen, I call BULLSHIT. I don't care who that president is. They simply seek to take credit for whatever their cronies in Congress and Senate can push into law. The role has become nothing more than a PR platform.

And in case you're wondering: yes, I have consumed a few beers in the past hour or two. None of which were less than 10% ABV, but it was all for a good cause: Me. ;)

Just another random thought.

Read More

Jobs. Jobs. Jobs. IT Jobs

My employer, Endurance IT Services, located in Virginia Beach, Virginia, is hiring.  Yes!


(2) Engineer (Tier II) - Windows/VMware/Exchange (Hampton Roads)


Looking for Systems Engineer with a minimum of 7+ years of hands on experience with diverse network environments.  This position is for a full time opening on our engineering team. This team is responsible for the design, installation and support of networks for numerous clients in Hampton Roads.  The typical environments include Microsoft Windows 2003/2008 Servers, Exchange 2003/2007/2010, Cisco routers/switches/firewalls and other 3rd party applications.  Bachelor degree preferred. Ability to assess and formally document client environments a must.


Key Skills include all the items below:

• Microsoft Exchange 2007 / 2010
• Windows Server 2008 / 2008 R2
• Active Directory
• Networking with various products

(2) Senior Engineer (Tier III) - Windows/VMware/Exchange (Hampton Roads)


Senior Systems Engineer with a minimum of 15+ years of hands on experience with diverse network environments.  This position is for a full time opening on our engineering team. This team is responsible for the design, installation and support of networks for numerous clients in Hampton Roads.  The typical environments include Microsoft Windows 2003/2008 Servers, Exchange 2003/2007/2010, VMware Vsphere, SANs, Cisco routers/switches/firewalls and other 3rd party applications.  Bachelor degree preferred.  Ability to assess and formally document client environments a must.


Key Skills include all the items below:

• VMware in HA environments
• Microsoft Exchange 2007 / 2010
• Windows Server 2008 / 2008 R2
• Networking with various products

We are looking for strong candidates with technical support skills and great interpersonal skills.



We are a fast growing company that is strongly focused on customer service and satisfaction. We are building a corporate culture which supports learning, growth and advancement in the Network Services career field. Our focus is solely network services.  We offer competitive salaries, a comprehensive benefits package, and a great place to work.

(A LOT of employers say the above mumbo-jumbo, but I will concur 110% that it is indeed a great place to work for.)



If you live within the Hampton Roads area, and are both qualified and interested in one of these available positions - contact me for more information at ds0934 (at) gmail (dot) com.

Read More

Top-Down vs Bottom-Up

I promised "more to come" yesterday, so here goes... (warning: mindless rambling begins now)

In general terms, within larger organizations (e.g. corporate or government environments), there exists two broad approaches to "software development":

• Top-Down
• Bottom-Up

Top-Down

When you have the luxury of working in a structured team scenario, especially (possibly ONLY) when it consists of talented people that ALSO get along VERY well, you can take the time to plan and proceed in a logical manner.  By this, I mean: gather requirements, assess the status quo against the desired outcome, determine gaps, resources, timelines, etc.  And you may even have the luxury of dedicated project managers, program managers, developers, architects, test groups, test procedures, CMMI and all that.

This notion of planning ahead, designing everything methodically, testing and more testing, is all part of the "top-down" approach.  This is the approach taught in schools, text books, lectures, and so on.  It's admirable and difficult to find fault in this concept.  But everything has potential drawbacks.

Bottom-Up

When you start coding within a short time of having an idea.  When you are faced with crisis-mode problems that demand your full attention to solve using whatever tools you have at hand.  When you don't have an elaborate structured environment to delegate tasks to.  When like to create and evolve something, rather than plan it ahead.  All of these reasons, and many more, often lead immediately into a "bottom-up" development process.  Oftentimes this approach ends up at a crossroads with Top-Down ideals, where the developer(s) stops at 2.0 or 3.0 and decides to refactor, clean-up, and document everything.  At this point, it often takes on a new direction that feels more like "top-down", even though it didn't start out that way.

So what's the best way to go?  There is no "best way".  There is only the "way" that works for your endeavors.  Sure, logically speaking, it's hard to argue that with all the right pieces in place, that a "top-down" process isn't the better option.  But a lot (repeat A LOT) of developers do not have such luxuries.  And even more of them have personal leanings towards "bottom-up" because it suits their creative process.  Is that wrong?  Who knows.

I've worked in both camps for quite a bit of time.  There are aspects of each I like and dislike.  Sometimes I compare them to cooking with gas versus a wood fire.  One is simpler to get going, the other has a nicer feel to it.

One subtle, often overlooked, yet serious drawback to the "top-down" approach is the timeline.  With a more rigorous application of metric-oriented planning and execution comes a long duration (start to finish).  While that may seem like an obvious cost risk, the other side of this (the part I propose as being "overlooked") is the budget window constraint.  I've seen plenty of large-scale development projects fall to the cutting room floor because the timeline ran afoul of an ever-scrutinized budget.  Many times it happens before any code has been written.  Great ideas on paper, in a server shared folder, in SharePoint or some other repository, being hashed and vetted and showing immense promise, only to slide unknowingly under the falling axe of a budget cutback.

On the flip-side is the "bottom-up" approach.  Sometimes viewed as "shooting from the hip" or "wild west show' approach.  Get the code moving sooner and work out the kinks as they come up.  Give and take with the end users.  It is exciting to work in that fold.  I much prefer meeting users face to face than sifting through survey reports, forum threads, and e-mails. 

As Chris Curran states*: 

"While Agile and CMMI can coexist, there are limits.  Agile practices can normally function with CMMI levels 1 to 3 but are usually incompatible with the higher maturity levels 4 and 5. At CMMI levels 4 and 5, the intrusion of documentation into the development process over-formalizes Agile’s internal discipline and Agile ceases to be agile."

Everything has limits obviously.  You can't fit either of these approaches to every situation.  There are many stories involving Facebook, Twitter and other recent major ideas where the nexus of their success was taking an unorthodox or hybrid approach to their entire inception and debut.  Stop and think about every aspect of the way your are currently approaching software projects.  Are there things you wish could be improved?  Eliminated?

I need sleep.  Cheers!

* "Are Agile and CMMI Compatible?" - http://www.ciodashboard.com/it-processes-and-methodologies/agile-cmmi-compatible/

Read More