Because it’s Bad-Ass, that’s why…

Ok, not as visually exciting to watch as the Top Secret Drum Corps, or The Phantoms, but damn, this was just well done.  Bad Ass.  Enjoy!…

Windows 7, MSG.EXE and Group Policy Preferences

So, as of Windows Vista, NET SEND is gone.  But you want to send a console message via popup to a remote user or computer?  Windows Vista shipped with the MSG.EXE utility, which is still around in Windows 7.  But there’s a small problem, which led me to another small problem, but thankfully there’s an easy solution.

Problem 1 – You may need to modify a Registry Value on all your networked Windows 7 computers.

• HKLM\SYSTEM\CurrentControlSet\Control\TerminalServer
• Value: AllowRemoteRPC
• Required value: 1 (REG_DWORD)

Problem 2 – Trying to set that on a remote Windows 7 box

The Remote Registry service is disabled by default.  You can start turning on services manually, but…

Solution – Use Group Policy Preferences to do it all at once

1. Create a new GPO named something that makes sense
2. Edit the new GPO
3. Expand Computer Configuration / Preferences / Windows Settings
4. Click on Registry
5. Right-click and select New –> Registry Item
6. Select Action: Update, Hive: HKEY_LOCAL_MACHINE
7. Key Path: browse to the key shown above
8. Select the Value name: AllowRemoteRPC
9. Set the Value data: 1, specify type REG_DWORD
10. Click OK

If you also want to enable remote Registry editing…

1. Expand “Control Panel Settings”
2. Select “Services”
3. Right-click and select New –> Service
4. Startup: Automatic, Service Name “Remote Registry”, Service Action: Start Service
5. Click the Recovery tab
6. Specify First and Second failure action as “Restart the Service”
7. Specify Restart fail count after to 1 day, Restart service after 1 minute
8. Click OK

I think I may need a kleenex

Adios SMS and System Center

After years of working with, consulting and being involved with Microsoft SMS and SCCM I feel it is time to cut loose my involvement with that world. There simply are no opportunities whatsoever within my geographic area to even consult anymore. I have a good job that involves Wise packaging and scripting, but our parent company dictates Altiris. That won't likely change anytime soon.

I remember first working with SMS 2.0 back in the late 1990's with a good friend who passed away not long ago. My next project was a multi-site Active Directory migration to WS03 which was followed by my first SMS 2003 rollout. I actually joined the beta early on and received authorization to go ahead into production. It was exciting and scarry and I enjoyed every minute of it.

After that I spent a lot of time creating web reports, writing scripts, customizing MOFs and automating our inventory and patch management systems.  After a few years of growing with a growing company, the owner decided to cash out and split the place in half and sell it off and soon everything I worked on was gone or shut down.  I left to work for a consulting company that promised to put me to work in the area doing more SCCM work, but they never did any marketing and we floundered.  I ended up driving ridiculous miles to stay employed, but that fizzled out and nobody was doing any SMS or SCCM work within 150 miles of where I live.  None.  Zip.  Zero.

I worked hard on the SCCM beta and even passed the 70-401 MCTS exam for System Center Config Manager.  I’ve been watching the news from MMS 2010 and it looks like things are still progressing nicely.

As much as I enjoyed working with that side of the house, and spending time at MyITForum.com and other sites, it’s just not practical anymore.  I wish anyone who works with the System Center product line the best and hope that their jobs are prosperous.  However, I think it’s time for me to move on to other things.  Long live Wally Mead. :)

10 Things Software Vendors Just Don't Understand

After working with packaging and deploying software applications to a bazillion computers for several years, I've compiled some thoughts. Here goes: it seems that there are some consistent problems with software vendors views of customers and customer environments. The bigger problem is that they don't seem to be "getting it" any better now than in the past. In fact, with the economic pressures being applied on their end, I doubt they care to "get it" at this point, but maybe they will in the future...

1. Our client computers do not have INFINITE hard drive capacity.

2. Our client computers do not have INFINITE memory capacity either.

3. Not all client computers have Internet access (pssssst: here's a secret: some computers have to run in isolated environments to keep bad folks from messing with them).

4. Their products are not the only products we deal with.

5. Their products are not the only products installed on a given computer. There are others. Amazing, isn't it?

6. Unattended/Silent installs and uninstalls are very important (we don't like manually doing this on 20,000 computers. Seriously)

7. Sometimes users don't have Administrator or Power User rights.
Amazing, isn't it?

8. Sometimes we don't want your products checking for automatic updates.

9. Your developers should try to follow at least some of Microsoft's guidelines. It helps customers and helps you as well.

10. Releasing version upgrades more than once per year is not helpful.