Tuesday, August 30, 2011

System Center Configuration Manager

We've had a good bit of discussion lately about Microsoft's Enrollment for Education Solutions and the potential benefits a school district might experience if they were to choose to enroll. My mindset is that the yearly cost could be worth it if a district had full intention of utilizing many of the products for which CALs are included with this agreement. One product with great potential for school districts is System Center Configuration Manager (SCCM).

The potential benefits are listed on the linked page. With SCCM, districts could deploy operating systems (bare-metal imaging) which should lead to faster deployment. Software distribution would become completely automated. This should lead to a tool that can help you manage your IT hardware and software inventory much easier - "asset intelligence" is the buzz phrase here. In addition, the SCCM tool suite should allow for easier remote diagnosis and repair of machines. What's not to like, right?!?!

This is my slight beef and the reason for my post. I've talked to multiple districts that have deployed SCCM. I've spoken with a Microsoft contact about SCCM deployment. In virtually every case, the input I receive is that the product is wonderful but that it is a challenge to set up. One district outsourced the installation and initial setup, which may be advisable. When I asked another district if they set up SCCM themselves, here's a section of their reply:
...it is difficult. I will say I would not recommend it for an (inexperienced) district. It takes a lot of planning and it’s good to have a lot of experience with deploying Windows and applications. It’s a very big learning curve... It also takes diligent users to operate SCCM and understand how it works because it can be extremely dangerous if used improperly in an environment and I’m not using that word lightly. I do recommend it however and it makes everything extremely easy and it takes a huge load off of you after you set it up and get everything working.
All of that caution from a district that likes the product! Honestly, I get the caution about the power of such an administrative tool. I'm struggling with the difficulty of the setup. I see it as a huge barrier to adoption in my area. I'm certain I have districts that need to be using such a product. Some may even be convinced to spend the money to license the product either directly or via EES. With such cautionary tales of setup trouble and limited budgets to pay for configuration, I think some districts are being scared away from actually deploying a tool like this.

I'd like to see my districts using technology tools to make their lives easier. This seems to fit the bill, so I suppose the market is ripe for someone to come forward and bridge the gap between purchase of the tool and easy use of such a product.

Tuesday, August 16, 2011

TeamViewer

I have a district that swears by TeamViewer for a remote desktop solution. I won't say too much about it because I haven't used it first-hand, but I'm told that it's very easy to set up and begin using. It's often nice to have software that can do other things like file transfer and a 'presentation mode' where you show an end user (or users) YOUR desktop. The TeamViewer product seems to have that as well.

Their website and various reviews talk about cross-platform functionality and accessibility through firewalls and via a browser. It also has a "lifetime license" (e.g. you buy it, you own it) rather than a yearly subscription fee. Their advertised price for a business license is $749, though I'm not sure if an educational discount is available.

If you're looking for products in this space, you might give this one a look. As I said, one of my technical "go-to" contacts is very high on this product.

Wednesday, August 3, 2011

If you leave tomorrow...

I didn't begin this entry thinking of a way to link to Lynyrd Skynyrd's "Free Bird" or this version being played on a ukelele - suffice to say you can find anything on the Internet. I was actually thinking about the things you need to have available if you were to leave your technology position tomorrow. Too many of us get so caught up in our work that we haven't documented things in the event that someone else were to need to take over. What would be required?

* Passwords - Domain and/or local workstation and server admin passwords. Passwords for core network equipment, phone systems, security systems, web sites, third-party resources and the like. Think about the passwords you enter over the course of a month and make note of their purpose. Note the password and its purpose somewhere.

* Critical contacts - Who are your go-to people in terms of vendors and partners that you work with? Sure, you may leave your entire contact list behind, but who are you regularly working with to get your tasks accomplished? Who are your preferred vendors for various components that require service?

* Service contracts and agreements - What products and services are coming from your budget on a regular basis? When does the agree renew or need to be re-bid? If you left, would anyone else know about these arrangements?

* Management software - What products do you use to manage your environment? Do you have a list of basic processes along with instructions on how to perform basic tasks? We have much of that in our heads, but taking the time to document some of the basic steps might be helpful in the event that you leave on a temporary or permanent basis.

* Scripts and other automated processes - Will the next person know how to determine what you've automated? Does that script need to run for everyone or only certain users?

* Physical access - Do you have keys or codes to access data centers, outlying wiring closets, vehicles, buildings or other rooms that require restricted access?

* Access to critical files, both physical and electronic - I know that the federal E-Rate program requires documentation to be kept for several years. Is this somewhat organized and in a known location? If you're like me, you also have critical emails, documents and spreadsheets that your replacement might need. Are these organized and accessible?

I'm sure there are other items that I'm not mentioning. If you're fortunate enough to find a better opportunity, try to leave your position in a better place than you found it. Give your replacement more than you had on your first day.