Disabling InfoCenter in AutoCAD 2013

Owen Wengerd has done it again.  He's updated his free utility for killing InfoCenter for AutoCAD 2013.  Get it here: http://otb.manusoft.com/2012/03/turning-off-infocenter-in-autocad-2013.htm?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+obox+%28Outside+The+Box%29

Read More

VLDB Code Example: Reload Profile From .ARG

Another set of code from Chapter 19, of my book "The Visual LISP Developer's Bible (2011 Edition)" available on Amazon for Kindle and Kindle Reader apps.  This one reloads an existing AutoCAD Profile from a source .ARG file.  As you may know, if you load an .ARG file, it is imported into the Registry.  Each time you launch AutoCAD, if the shortcut or command line specifies /P to specify a Profile (even a full path to an .ARG file) if a Profile already exists (by the same name) in the Registry, the .ARG file is ignored and the Profile is loaded from the Registry.  This is pretty much the same way a web browser cache works when loading stored images.  If you want it to force a reload from the source .ARG file, here's one way to do it...

;;; Reloads a profile from an ARG file
;;; Replaces existing profile if defined
;;; Returns profile name if successful, otherwise returns nil

(defun Profile-Reload (name ARGname / bogus)
    (cond
        ( (and
            (Profile-Exists-p name)
            (findfile ARGname)
        )
            (if (/= (strcase name) (strcase (vla-get-ActiveProfile (AcadProfiles))))
                (Profile-Delete name)
                (progn
                    (setq bogus "bogus")
                    (Profile-Rename name bogus)
                )
            )
            (Profile-Import name ARGname)
            (vla-put-ActiveProfile (AcadProfiles) name)
            (if bogus (Profile-Delete bogus))
                name
        )
        ( (and
            (not (Profile-Exists-p name))
            (findfile ARGname)
        )
            (Profile-Import name ARGname)
            (vla-put-ActiveProfile (AcadProfiles) name) 
            name
        )
        ( (not (findfile ARGname))
            (princ (strcat "\nCannot locate ARG source: " ARGname)) nil
        )
    )
)

;;; Renames an existing profile
;;; Returns new profile name if successful, otherwise returns nil

(defun Profile-Rename (from to / result)
    (if (Profile-Exists-p from)
        (if (not (Profile-Exists-p to))
            (cond
                ( (not
                    (vl-catch-all-error-p
                        (setq result
                            (vl-catch-all-apply
                                'vla-RenameProfile
                                (list (AcadProfiles) from to)
                            )
                        )
                    )
                ) to ; Return new name if successful!
            )
        )
    )
)

;;; Deletes an existing profile
;;; Returns T if successful, otherwise returns nil

(defun Profile-Delete (strName / result)
    (if (Profile-Exists-p strName)
        (cond
            ( (not
                (vl-catch-all-error-p
                    (setq result
                        (vl-catch-all-apply
                            'vla-DeleteProfile
                            (list (AcadProfiles) strName)
                        )
                    )
                )
            )
            T ; return T for success!
            )
        )
    )
)

;;; Imports a profile from a given ARG file
;;; Returns profile name if successful, otherwise returns nil

(defun Profile-Import (argFile strName / result)
    (cond
        ( (findfile argFile)
            (cond
                ( (not
                    (vl-catch-all-error-p
                        (setq result
                            (vl-catch-all-apply
                                'vla-ImportProfile
                                (list (AcadProfiles) strName argFile vlax-True)
                            )
                        )
                    )
                )
                strName ; return new profile name if successful!
                )
            )
        )
    )
)

;;; Determine if profile name is already defined (exists)
;;; Returns T or nil

(defun Profile-Exists-p (name)
    (get-item (AcadProfiles) name)
)

;;; Return Profiles collection object

(defun AcadProfiles () 
    (vla-get-profiles (vla-get-preferences (vlax-get-acad-object)))
)

The Visual LISP Developers Bible – 2011 Edition
http://sites.google.com/site/visuallispbible
Copyright ©2002-2010 David M. Stein, All Rights Reserved.

Read More

VLDB Code Example: Purge All Opened Drawings

This little chunk of code will run a Purge on all drawings currently opened in your editor.

(defun AllDocs-Purge ( / docs)
    (vlax-for dwg (vla-get-Documents (vlax-get-acad-object))
        (vla-PurgeAll dwg)
    )
)

Read More

Windows 8 - What I Think About It

Your first thought was probably: "Who cares?"

Exactly.   But in case you might, here's what I think of it thus far:

It's aimed at consumers.  Nothing Earth-shattering about that.  Everyone else is already saying that too.  But it's not just that.  It's that it is suffering from a similar problem with Windows 7 in the early days: Marketing Stupidity.

That's right.  Most people don't recall how feeble the business marketing effort for Windows 7 was at the start. It was entirely aimed at home users.  All the ads were about how easy it was for kids to use, and how cool it looked.  IT professionals, meanwhile, were left to scramble for their own devices when it came to rounding up a business case to sell to their management for getting away from XP.  It wasn't pretty.

Windows 8 is doing the same thing.  All the marketing artillery is lobbing shells at the consumer side.  Tablets and Metro and Apps Market, and more Tablets, and Cloud this and Cloud that.  When the CIO and CFO pull up a chair and ask:  "Ok.  What the fuck about this Windows 8 is going to make us a better company?"

Most of us will say "Well... uh.... umm..... I'm still looking into that."

Fwamp Fwamp Fwamp...

Here's what Windows 8 needs to have before I could get behind any effort to woo the CFO to stroke a big check to embark on yet another upgrade project (remember, many businesses are still in the midst of a Windows 7 upgrade effort):

1. A "Windows 7 Classic" theme, that looks EXACTLY like Windows 7.  For businesses to roll-out onto their already shell-chocked XP-to-7 users.  Then we can shift to Metro later when the Xanax runs out.
2. A native App-V client included in the base product.  App-V is cool, but I'm really sick of how hamstrung it is within MDOP and EA/SELECT and it's really holding back a lot of potential.  Sick isn't the word.  Disgusted is more like it.
3. A native MED-V feature as an option.  My feeling is the same as described for App-V.
4. A better approach to COM activation than DCOMconfig.
5. A better solution to keep the Registry clean

I'm stopping here because, although I could go on (much longer), it would behoove myself to just say it needs to offer a wide range of improvements to literally make Windows 7 seem as outdated as 7 did for XP.  Right now, it's not there.  Windows 8 is a minor step from 7 in most respects.  Sure, it's got a lot of cool stuff and a new UI, but from a ROI perspective, you really have to dig like a starving animal in the desert to find enough to build a strong business case for going from 7 to 8.  Even from XP to 8 doesn't make as much sense at this point as going from XP to 7.  The jury is still out obviously.  I'm probably casting my vote prematurely, and I will give it time to mature.  I will revisit this argument when it gets closer to final release.

Read More

VLISP Housecleaning: Example 2

Here is another example from my ebook, "The Visual LISP Developer's Bible, 2011 Edition" (Amazon Kindle).  This one demonstrates a shell process, whereby the code executes an external COM interface request to use VBscript to perform a simple date calculation.

(defun daysold (d / sc cmd result)
    (setq sc (vlax-create-object "ScriptControl"))
    (vlax-put-property sc 'Language "vbscript") 
    (setq cmd (strcat "DateDiff(\"d\", \"" d "\", Now)" )) 
    (setq result (vlax-invoke-method sc 'Eval cmd)) 
    (vlax-release-object sc) 
    (eval result) 
)

(setq age (daysold "12/1/2010"))

You can do the same with JavaScript (actually JScript) as well.

Read More

VLISP House Cleaning Project

I've said before that I'm pretty much retired from writing books about AutoCAD or AutoLISP/VisualLISP, but I still get e-mail from readers asking for help or to share some code.  So, since it's not exactly ideal to make use of the code in my ebooks, I've decided I will post some (not all) of the examples from "The Visual LISP Developer's Bible, 2011 Edition" on my blog over the coming weeks.  As time permits, anyway.

To kick this off, here's the example from Chapter 21, exporting a drawing layers table to an Excel spreadsheet using Visual LISP and the COM interface...

(vl-load-com)
(setq acad (vlax-get-acad-object)) 
(setq activeDoc (vla-get-ActiveDocument acad)) 
(setq layers (vla-get-Layers activeDoc))
(setq excel (vlax-create-object "Excel.Application"))
(setq workbooks (vlax-get-property excel 'Workbooks))

(princ "\nSetting visible to True")
(vlax-put-property excel 'Visible :vlax-true)

(princ "\nGetting active workbook...")
(vlax-invoke-method workbooks 'Add)
(setq workbook (vlax-get-property excel 'ActiveWorkbook))

(princ "\nGetting active worksheet...")
(setq sheet (vlax-get-property excel 'Activesheet))

(princ "\nRename active worksheet...")
(vlax-put-property sheet 'Name "Layers")

(princ "\nGetting cells...")
(setq cells (vlax-get-property sheet 'Cells))

(princ "\nPrinting column headings...")
(vlax-put-property cells 'Item 1 1 "LayerName")
(vlax-put-property cells 'Item 1 2 "Color")
(vlax-put-property cells 'Item 1 3 "Linetype")

(princ "\nPopulating cells...")
(setq row 2)
(vlax-for layer layers
 (vlax-put-property cells 'Item row 1 (vla-get-Name layer))
 (vlax-put-property cells 'Item row 2 (itoa (vla-get-Color layer)))
 (vlax-put-property cells 'Item row 3 (vla-get-Linetype layer))
 (setq row (1+ row))
)

(princ "\nSaving workbook...")
(vlax-invoke-method workbook 'Save)
(vlax-invoke-method workbooks 'Close)
(vlax-invoke-method excel 'Quit)
(foreach obj (list cells sheet workbook workbooks excel)
 (vlax-release-object obj)
)
(gc)
(prince "\nDone!")

Read More

The Mid-Level IT Manager

If you've worked in any industry, you're probably aware of what a "mid-level manager" is.   You may also be aware of how subjective the term "mid-level" is, especially as the size of an organization grows.  There are often many levels of "mid-level".

The interesting aspect that comes into to play is when people move from a non-managerial level into a managerial position, of any level.  I've seen and experienced it, from various angles, in the service industry, construction, engineering, sales, legal, medical and IT organizations.  The IT organizational aspects are most interesting to me.  Why?  Let's digress a bit...

The entire life of most entry-level workers is usually some sort of "hands-on".  It was often the sole reason they pursued the line of work in the first place.  I'm not counting people that take "any job" because they need a paycheck.  Those folks don't typically stick around long enough to move into any managerial roles. The folks that move into management positions are usually "career oriented" rather than "job oriented".

For years, the diligent line worker, systems administrator, programmer, analyst, technician, systems engineer, even systems architect, plies his/her trade and struggles to keep pace with ever-newer technology and trends.  Hours and days spent in labs, at home, learning, testing, experimenting.  I'd guess on average we spend probably a solid week of our life every year doing things to improve our skills.

Then one day, you're called into an office and asked to close the door.  Instead of the expected ass-chewing, you're greeted with a smile and a congratulations.  Sometimes bundled with a few solid minutes of accolades and commendations for worthy achievements.  Then the punchline: "We want to promote you to Team Lead/Manager, etc."  At first you're ecstatic, because you've had a train-load of sunshine blown up your ass with a smile and a hand-shake.  They calm your fears about handling the new duties, the paperwork, the meetings, the new agenda.  You soak it up over the weekend.  You show up on Monday and start picking away at the new world ahead of you.  Life moves on.

After a few months you realize you miss working on the things you used to work on.  There's a touch of emptiness.  A bit of isolation, now that you're working with a new group of people, and your circle of faces is morphing into a new entity altogether.  Some might even say it's a sign of depression.

But that's not unique to the IT world.

What I've seen that is unique to the IT world is the extreme level of self-worth tied directly to the "hands-on" achievements.  You don't see that in construction.  You don't see it at that level in most any other line of work.  An IT engineer/technician/programmer/analyst assesses their value by virtue of what technologies they've mastered, what projects they've been instrumental in accomplishing, and how their professional-social (combined) circle values their capabilities. That's right.  It's a bit of a vanity and ego twist, but we do very much value what our peers think of our abilities.  We absolutely do NOT want to be the guy who gets joked about for screwing things up.

Now that person is asked to step away from that zone, and into an entirely unfamiliar zone.  A new zone where self-valuation is based on entirely new skills and new methods of assessment.  It's a major shift and it often causes problems for people trying to cope with a multi-faceted group of changes:

• New peers
• New duties
• New skills
• New assessments
• New schedules
• New agendas

Shit.  Even one or two of these can be very disruptive to a person.  Emotional and physical.  But when you've spent years tying yourself strongly to each of these, and ALL six of them are swapped out... wow!  For a non-IT person, it would be like...

• Moving to a new house
• ...In a different country
• ...On a different planet
• ...In a different climate
• ...Using a different language
• ...and Changing your name

Some can cut it.  Some can't.  Some relish the new role.  Some despise it.  Some find peace and comfort.  Some find angst and turmoil.  It really boils down to one basic issue...

Are you happier working with "things" or with "people"?

Most IT folks I've known over the years, tend to favor "things".  Mainly because it's a technical field of work, that requires hours and hours of intimate time with "things" in order to figure them out in excruciating detail.  They're often more at ease in a quiet room surrounded by stuff: hardware, or software.  Or behind a computer screen typing away at code.  The more intimate our relationship with our technologies, the more isolated we often become.  Compare the average day of a network engineer, server administrator, or programmer with someone in construction, fast food service, sales, or other fields, and you'd likely find the IT person spends much less time with much fewer people each day.  It's usually referred to as "the nature of our work".

That leads into the dilemma of making the shift from working with technology to managing people.  It's entirely different.  Some have the desire and the natural tendency to make that jump, but more often it's a very tough transition.  I've known quite a few colleagues over the years who've tried to make that switch and only a few stayed with it.  Most of them moved back into a technical role and were happier.  I suppose the inverse would be true as well:  Try to move a non-technical manager into a role where they spend most of their time putting things together in a data center, by themselves or with one other person (the most common scenario I've seen).  That, too, would be a difficult transition to get used to.

Conclusion

So, having said all this, what I really need to say is that when you are dealing with a mid-level IT manager, especially one who has only recently made the transition, be considerate.  It's tough.  Very tough.  And you may find them to be a bit awkward and uncomfortable at times.  Give them time to adjust and a little room to figure out what they're doing.  It may work out just fine.  Too often others are quick to judge against them, and that only adds to the angst and frustration, making a difficult situation even worse.  If they're a complete dick, that's one thing, but if they're just awkward, even at brief moments, try to be understanding.  I say this because:  when that transition works, it works great for everyone.  Nothing beats a manager that truly, honestly, thoroughly "gets it".  They've done your job, or worked at a peer level, long enough to know what it means for those still doing it.  Nurture a manager like that, and it comes back around in good ways.

Read More

LDAP User Account Properties: The WMI way

This is just something I ran across working on a recent project.  You can replace "." (local computer) with any valid NetBIOS name on your network (as long as you execute the script code with sufficient privileges to access the WMI Namespace)

[code]

strComputer = "." 
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\directory\LDAP") 
Set colItems = objWMIService.ExecQuery("SELECT * FROM ds_user",,48) 
For Each objItem in colItems 
    Wscript.Echo "-----------------------------------"
    Wscript.Echo "ds_user instance"
    Wscript.Echo "-----------------------------------"
    'Wscript.Echo "DS_objectGUID: " & objItem.DS_objectGUID
    'Wscript.Echo "DS_objectSid: " & objItem.DS_objectSid
    Wscript.Echo "DS_pwdLastSet: " & objItem.DS_pwdLastSet
    Wscript.Echo "DS_sAMAccountName: " & objItem.DS_sAMAccountName
    Wscript.Echo "DS_sAMAccountType: " & objItem.DS_sAMAccountType
    Wscript.Echo "DS_whenCreated: " & objItem.DS_whenCreated
    Wscript.Echo "DS_whenChanged: " & objItem.DS_whenChanged
Next

[/code]

Note that I commented out the GUID and SID properties.  That was for simplicity. You can fetch them to a variable, convert them to an appropriate data type, so that WSH / VBScript can correctly "echo" the results.  Cheers!

Read More

IAQ Time

You've heard of Frequently Asked Questions, or FAQ's.  But an IAQ list is for Infrequently Asked Questions: The questions that are rarely asked.  That doesn't have any correlation with their importance, however.  It just means that they don't get asked as often.

Why run Active Directory at home?

There are a lot of good reasons actually.  Let me itemize just a few:

- Time and Computer Restriction

If you have kids, you can set their allowed logon and logoff times per day of the week, in one place and it applies wherever they use a computer on your home network.  If they like to sneak onto your other kids' computers, or those of you or your spouse, you can easily lock their accounts down to only one computer.

- Account Management

Rather than making a "Josh" account on three computers and leaving a stale password on all three, you can make one "Josh" account and turn on password policy to force them to change it on a set number of days, and force them to use a complex password.  Go ahead and laugh, but I've seen a lot of home computer hacked into because the users had stupid (or blank) passwords.

- Authentication

Tired of setting up a "Josh" account on three computers so your son Josh can play games on one, save pictures to another, and send print jobs to another?  Well, a single AD account and simple group features will take care of that and leave you plenty of time to do more exciting things, like mowing the lawn.

- Group Policy

Easier configuration management.

Why use WSUS at home?

Two reasons: Better Control, and it's FREE.  You can approve more types of updates for automatic installation than you can with Automatic Updates (aka "Windows Update", aka "Microsoft Update").  If you don't believe me, and you're still using Automatic Updates, and you believe your computers are patched up completely, visit the Microsoft Update site again, and check again.  You could have automatically approved and installed all of them in one place, for all of your home computers, and moved on.  Oh yeah, and it's free.

Why use a Router at home?

If you plug your computer directly into your cable modem, all I can say is "good luck!".  We did some testing in one our labs at an office I used to work at, where we plugged in an XP SP3 computer without a router/firewall, and it was hacked and owned within 45 seconds.  After three more tests, the average turned out to be 50 seconds.  Using Windows Vista, in default configuration, it took about 1 hour and 20 minutes on average.  We didn't test with Windows 7 because it wasn't out yet.  But you get the picture, hopefully.

Most modern home network routers provide a decent firewall capability out of the box.  Nothing is perfect, after all, hackers have penetrated firewalls of some of the biggest corporations, the U.S. military, and even the FBI and CIA web sites.  But then again, the stakes are much higher, so the appeal of hacking those is much higher than anyone wanting to hack YOUR home network (unless you're the CEO of a big company)

Whether you prefer Linksys, Cisco, Netgear, D-link, or whatever, most of the routers sold today offer a fairly good firewall and other features to help secure your network.  They're cheap too.  Use them.

What is the point of following politics?

Politics is an elaborate game designed to keep the public distracted from two main problems in our lives:  (1) Most people aren't happy and are bored, and (2) it makes them believe they have some influence on the outcome of elections, and therefore, some influence on government action.  Once they realize that (2) is false, they occupy that time with things like watching TV shows, sports, and regular consumption of drugs and/or alcohol.

Why doesn't Dave follow a franchise Sports Team like everyone else?

Because I've learned over the years that fans value the team about 10X more than the players do.  Dangle a better contract in front of any NFL, NBA or MLB player and they're gone like a dog chasing a stray chunk of lunch meat.  You can't buy fans away from their favorite teams, but the players, or rather "contractors" (let's face it, that's what they are), have no such allegiances.  The whole thing is disingenuous.  I watch games for pure entertainment value.  I don't give a flying crap who is getting traded to whom, or what so-and-so stats are.

Why does anyone read this blog?

I'm still trying to figure that out.

Read More

SxSWi Article

During my brain drain hiatus I've been working, reading, and absorbing things to keep my one-celled brain busy.  Here's a really good article by Josette Rigsby on the future of mobile development as it permeated SXSW this year:  http://www.silverstripe.org/predicting-the-future-of-mobile-development-at-sxswi/

Read More

Software Distribution - What is does it mean?

Maybe you've seen job postings for "Software Packager" or "Software Deployment Specialist" or something like that and wondered what it's really about.  Maybe not.  Maybe you just don't care.  Maybe you're working in the IT industry, but you're not happy with your current situation.  Maybe you still don't care.  Maybe I don't care either.  No.  Forget that. I care.  I care enough to write this article and bore you to death.

Software Distribution / Deployment, is really about automating the process of installing software on multiple computers over a network.  That's it in a nutshell.  It breaks down into much more detail, but that's the 50,000 foot level overview.

What do you need to know?

First off, you'll need a pretty solid understanding and familiarity with the Windows platform.  The file system, NTFS, permissions, the Registry, Registry permissions, services, processes.

Secondly, you'll need a fair understanding of installing and uninstalling software.  Whether it's using MSIEXEC, or some setup.exe (InstallShield, Wise or homegrown crap), as well as dealing with components (DLL, OCX, etc.) and registration (REGSRV32.exe).  You should also be familiar with uninstalling and how folders and files are handled (or not) during the removal process.

Third, you'll need a fair understanding of basic scripting techniques.  Things like IF, THEN or ELSE are always helpful, since they imply a basic workflow logic, which is how all installers are constructed.  For example, "IF does not exist, then install it, ELSE skip to step 43..." and so on.  Whether you're more familiar with .BAT or .CMD, or .VBS scripting doesn't matter.  It's the same basic logic that matters.


Bonus:  InstallShield Editor, AdminStudio, (even Wise Package Studio, rest its poor soul).  WMI. Really solid scripting experience (BAT or VBS is fine).  Familiarity with switches for setup.exe installers.  Familiarity with common software installation options like Java Runtime (JRE), .NET 4, Oracle Client, SQL Native Client, Adobe Flash Player, Microsoft Office 2010, Adobe Acrobat Professional,

Command Shell:

• REG.exe
• REGSVR32.exe
• CACLS.exe
• DEL
• COPY, XCOPY or ROBOCOPY
• MD and RD
• ATTRIB (rarely)
• SC (rarely) or PSSERVICE *
• TASKKILL or PSKILL*
• Sysinternals (*):  PSLIST, PSKILL, PSEXEC, PSSERVICE
• REGINI (rarely)

Tricks:

• setup.exe /r (or -r), along with -S -F1, -F2
• Extracting files from bundled installers (WinZip, 7-Zip, etc.)
• Searching for installed components before installing them again

What tools do you use?

You will most likely use a mix of the following types of tools:

• A computer with LOTS of memory and an extra hard drive
• A virtualization product (VMware Workstation, VMware Player, Virtual Box, etc.)
• A text editor (Notepad, TextPad, DevPad, Ultra Dev, maxipads, minipads, whatever)
• A capturing tool (Flexera AdminStudio / Repackager)
• A setup editor (Flexera InstallShield Editor)
• A Transform editor (Flexera InstallShield Editor and/or AdminStudio Tuner)
• AppDeploy.com
• MyITForum.com 
• Coffee or Red Bull
• Sugary or Crunchy snacks
• Music (with headphones)
• A comfortable chair

What drives the work?

The business drivers come from various sources:

• Cyclical upgrades (new version of the same product)
• Cyclical updates (hot fixes, patches, etc.)
• Windows 7 compatibility (not very often anymore, actually)
• Configuration changes (enable/disable features)
• New Products (purchased)
• Allocation Changes (moving installation from user-to-user, or machine-to-machine)

Where are the opportunities?

Across the United States.  Even right here in Virginia Beach, Virginia.  In addition, the following locations have been solicited at me by recruiters over the past six months:  Arkansas, Oklahoma, New Jersey, Colorado, Florida, Maryland, Delaware, Ohio, Illinois, Rhode Island, Vermont, and Louisiana.  If you want to get spammed too, just post your resume on Dice, Monster, CareerBuilder, and watch the spam fly at you.  Make sure you update your resume accordingly first, however.

What are the advantages to this role?

Unlike many other jobs, software repackaging and deployment are often self-paced and self-managed tasks.  Very few positions will involve any sort of micro-management.  You are most often judged on the output results.  You'll get to explore the guts of Windows in ways you never imagined, but do so in a way that leads to a goal, rather than wandering around aimlessly.  It is indeed a learning experience.  A very interesting learning experience.  You will learn more about file system security (ACL's), the Registry, Registry data types and Registry security permissions, WMI, command line tools, Sysinternals tools, Windows Installer processing, user context, processes and tokens, services, and much more.

What are the disadvantages to this role?

The big-name software companies have very good resources for documentation, support, downloads, knowledge base articles, etc.  Smaller companies however, tend to suck at it.  You will spend more time on the little bullshit applications which were not packaged with a standard product like Wise or InstallShield.  These are also the source of the most common products that require repackaging (snapshot or monitoring).  Their phone reps (if they have any) will insist that all of their customers give all of their computer users full Administrator rights to their computers.  They will tie their products to bullshit pre-requisites and components which are outdated or code for things like "user must be 'Administrator', not AN administrator" and more idiocy like that.  You will smack yourself in the face enough times to use a good facial moisturizer.

Read More

State of the Tech Industry: Sort Of.

Here's my two-cent predictions:  Keep in mind that I don't own stock or any vested interest in any tech company.  My employer is a partner of Microsoft, VMware, Cisco, HP, NetApp, and others.  We work on all major platforms, and my personal role is in the area of software deployment automation and business systems automation.  We don't sell hardware or software.  We sell services.  Ok, enough of the disclaimer crap...

Regardless of the blabbering from all of the Android tablet vendors, Apple will remain comfortably in the lead of the tablet market for at least the next two years (out to 2014 at least).  Android tablets won't even match it in terms of sales or market share (for similar form factors).  iPad will remain on top of the market for a long time to come.  This isn't just my view.  It's also the view of most major tech industry analysts.

Microsoft will make major gains in server virtualization when Windows 8 Server Hyper-V ships, which will cause EMC/VMware to cut prices and shift their pawns on the board to avoid losing customers.  Cost alone will be a huge weapon, especially when reviews start pouring in about Hyper-V's improved features, scalability, reliability and uptake.

Microsoft will make smaller, but noticeable, gains in market-share against Oracle with SQL Server 2012.  The new features and capabilities, combined with the much cheaper cost, will be hard for cost-conscious customers to ignore.  It will be slow gains at first though.

Flexera Software will continue to prosper from the looming death of Wise Package Studio and the ignorant stupidity of Symantec.  There is now an effective monopoly in the software packaging and repackaging market, but it's under the RADAR of almost everyone, so they will slide through comfortably to a nice profit margin.  More businesses are adopting FlexLM and FlexNet Manager products as well, so support revenues will continue to grow at modest rates.

Windows 8 uptake will be slow but respectable in the consumer market.  In the business/enterprise market however, it will be negligible.  Not because it's a bad product or anything like that.  Here's why:  Most businesses are JUST NOW ramping up to migrated to Windows 7, which has bumped up budgets for hardware replacements, additional memory, hard drives, and other bandaids.  Most of them are in a position in 2012 where they're either far enough into Windows 7, that it makes no sense to shift into Windows 8 within the next year at the soonest.  Add to that those that are still on XP who see what Windows 8 CP reviews are shaping up to be.  It's being perceived as a pure consumer play.  Tablets.  Not for business desktops or laptops.  Some will buy it, but nowhere near has significantly as Windows 7 has seen.

Now, Windows 8 Server will be a different ball game entirely.  I see that making significant gains in late 2012 and early 2013.  Mainly because (A) a lot of customers have stayed on Windows Server 2008 and waited out R2, and (B) the new features in Windows Server 8 will woo a lot of them to skip R2 entirely, which wouldn't be a bad move.  There's nothing wrong with R2, but let's face it: There are few, if any, "gotta have" features in it for most businesses as it relates to the upgrade cost.  Windows Server 8, on the other hand, packs a pretty big punch.  The bang for the buck is on the side of Windows Server 8:

• Hyper-V 3.0 (with concurrent Live Migration, VHDX, etc.)
• Disk Data Dedupe
• AD integrated KMS activation
• DHCP redundancy
• Improved Clustering and Cluster Shared Volumes
• Claims Based Authentication
• SMB 2.2
• AD DC cloning
• Improved Branch Cache
• NIC Teaming
• Enhanced PowerShell 3.0 features (web interface, Intelli-Sense, etc.)  In fact, the entire OS is written CMD shell first, and GUI afterwards.  Sound familiar?
• A newer, leaner Core edition
• Trevor Pott does a good job of itemizing Windows Server 8.  Check it out.

Bing will continue to lose money for Microsoft, but they'll play a shuffle game with other OSD projects and roll in Xbox, Ad services, and Metro and make it confusing to isolate which hole is sucking the most revenue.

Someone will buy RIM, kill off the product line (Blackberry) and rape the IP treasure chest.  There's no future value in the products themselves anymore, but the patents are worth a ton.  Wouldn't it be poetically ironic if NTP were to acquire RIM?

Symantec and McAfee will soon begin the long, slow, depressing march to their deaths.  With Microsoft rolling ForeFront and Security Essentials evermore tightly into their products, at little or no cost to consumers, those one-trick ponies will be searching for new revenue streams, probably stepping into the Linux services market like Novell tried.  Look how well that worked for them.

We'll either keep Obama or get a new president, but nothing will change for any of us regular working folks. It never does.  It never will either.  Just keep watching your favorite TV show or sports games, that will keep you distracted and happy.

We'll continue to hear about Iran in the news for a long time to come, but the U.S. will do nothing militarily against them directly.  It will be another year of lip service.

Someone will find, capture or kill Kony.  Another Kony-clone will pop up within 15 minutes to replace him.

Gas prices will continue to fluctuate, but gradually rise through the Summer.  We will all bitch and moan like babies, but swipe our credit cards and fill up like good sheep.  Congress will pretend to "haul" the oil company executives in front of "panels" on TV, to act like they're slapping them around, only to appeal to voters and win another term.  Ultimately, nothing will happen to the oil companies and we will be happy to give them more of our money like good sheep do.

It's March 14, 2012.  Check back on this March 14, 2013 and see how well I predicted this mess.

Read More

Don't Be Afraid to Ask

Nearly every project I have ever been involved with, or even witnessed, in my lifetime, ranging in budget from a few dollars to millions of dollars, was usually dunked in the shit tank at some point because nobody spoke up at the right time to ask what it is/was they are really, ultimately, trying to accomplish and why.


It's as if there was a tribe of people marching along in a single-file line across a vast desert waste land, meandering all over, while following the foot steps of the person in front of them.  After miles of trekking, someone in the back of the line finally asks "where the fuck are we going?  why are we going this way?"  


This is critical.


This is where you see what an organization is really made of.  If the others in line turn and acknowledge that it is a worthy question, and take up the cause, you have a good group of people.  If they tell the guy to be quiet, you have a death march into the vast abyss of failure laying ahead of you.


If you read books by, or about, famously successful business people, visionaries, you will find a common thread is that they not only form a great team around them, but they listen to them.  Whether it's Lee Iacocca, or Steve Jobs, or Randy Pausch, they not only allowed for dissent to be voiced, they encouraged it.  Failure is going to happen.  It's how you recover that matters.  But if you force everyone around you to accept an opaque vision and a unclear direction, they often shy away from speaking up.  This breeds fear of failure, which breeds fear of taking risks.  Without taking risks, you can't make real progress.


If you're not sure what kind of environment you're really working in, just ask the basic questions, and not just once, but often.  Make sure you get a real answer, and not some rhetorical politi-speak.


"What are we ultimately trying to accomplish?"
"Why?"
"For whom?"


Most projects that falter, tend to focus on the "what", "when" and "where" aspects.  But without the "why" and "who", it's like a ship without a rudder.  Money will be spent and time consumed, mini-projects spawn and take on their own lives, people gain new career footholds at the expense of hooking the organization on yet another dependency they can't easily (or cheaply) cut loose.  Rice bowls.  Mini-kingdoms.  Politics.  All the poisons of a solid, progressive, quality-minded team.  Death by a thousand cuts.


Just ask "why?"

Read More

Windows 8 or Windows 7 R2 (?)

I ran the earlier "Developer Preview" for about a month on a bare metal install.  It was nice, but too buggy to keep using it beyond that.  I went back to Windows 7.


Then I downloaded the more recent "Consumer Preview" release, and followed the same process:

• Installed in a virtual guest machine for a few days to evaluate
• Back up my physical machine and create a repair disk
• Wipe and load the new OS on bare metal, formatting the entire hard drive

After a week, I have the following thoughts:

• The Consumer Preview is much more stable and reliable than the Developer Preview
• The new Start Screen interface (aka "Metro" or "tiles") is aimed at tablets only
• The new Start Screen interface doesn't offer any benefit on a desktop or laptop
• Some apps work only in "Desktop" mode
• Some apps work differently between Start and Desktop modes
• Most of the staple apps have not changed at all (see below)
• Windows 8 is really more like a Windows 7 R2

It has a new-ish interface, sort of, kind of, except when it jumps back to "desktop" mode for many apps.  Yes IE10 is a little faster, depending on which flavor of it you launch, but installing Flash, or other plug-ins is klunky unless using the desktop flavor.  Explorer finally has a ribbon. wow.  That could've been added to Win7 by a hotfix, but they held off until this.

A HUGE, I repeat HUGE, number of components and apps that ship with it were not upgraded or updated.  MMC 3.0, Event Viewer, Computer ("system") properties, Network Interface (sharing and etc.), Services, and nearly all the .MSC add-ins, are all the same as before.  I dare anyone to identify what was improved from WMP 11 to WMP 12 besides the version number.  REGEDIT, most of the command tools like SC, REG, CACLS, XCOPY, etc. haven't changed one bit.

Let's call it what it is:  A tweaked version of Windows 7 for tablets. 


If you're on a desktop it's really not a huge benefit.  The jury remains out as to whether the IT-oriented improvements are really better than Windows 7.  DISM, and imaging features saw some improvements, but beyond that?  We shall see.  It looks like the "consumer" in "consumer preview" is the clearest indicator that this isn't aimed at businesses or IT shops at all.  Purely a consumer play, which is fine, but the marketing hype needs to be viewed with Cap'n Crunch secret decoder goggles to filter out the marketing noise.

I'm expecting the Microsoft marketing machinery to do the same thing they did with Windows 7:  Focus on consumer and UI/UX features and completely ignore the (positive) business impacts, and IT management features.  Too bad.  When Windows 7 hit the streets, those of us in the IT world found ourselves digging up our own "what's cool" lists to convince management that upgrading to Windows 7 was worthwhile.  Given the revenue channels Windows follows, you'd think the focus would have been the opposite.  


Microsoft left IT professionals holding the bag on making our own business case arguments, at least during the first few months after release.  Later, of course, they gradually fed the enterprise customer pipeline more and more details about the improvements for their environments.


Let's hope they have something to offer business customers besides a cool touch-screen interface.

Read More

Don't be THAT Douchebag, mm-kay?

There are a lot of signs that you could be falling into the douche tank of life.  The douche tank is that vat of putrid ass-ness that people end up in by virtue of not using their brain.  We are all guilty of bad brain days, like bad hair days, they happen.  But when they become habitual, it's a sure sign of swimming in the douche tank.  Here's some examples...

Arguing about Technology

You get into debates over which operating system is better/superior/best/coolest/most-coolest/whatever.  You forgot that operating systems are tools, like you.  It's one thing to get sucked into a mindless debate like this for about fifteen seconds, but after one minute: you are a douche.  Snap out of it.  Drink a beer.  Get laid.  Do something to remind your one-celled brain that there's more to life than computers.  Trust me: there is.  You continue on arguing to the goal line and when you cross it, you are now a douche.

Political Blabbering

You blabber about which president is to blame over some particular issue you feel certain is destroying the country and all of mankind.  You forgot to wait for the weekends to use your plastic bong back in high school and you were stoned out of your one-celled mind in class all week.  That part where the teacher lectured you on the fact that the President does not have ANY unlimited powers, and that nearly every significant historical change that has come out of your government (besides gay sex phone call scandals) as actually the work of the House and Senate.

You start arguing like a machine gun, using bullets you soaked up from watching some news show that morning, and you start blaming "Executive Order" powers.  You were stoned on that Tuesday when the lecture was about how E.O. powers can be checked as well.  You also tried to feebly use that argument in defense of the issue you believe is destroying the nation, but you forgot to check if that issue had anything to do with E.O. actions, and it didn't, and now you are a major douche.

Religious Blabbering

Nobody gives a flying shit what you think.  You know how I know that?  Because nobody gives a flying shit what I think either.  In truth, none of us really knows anything.  We think we do.  Thinking we know something that we really don't is the most dangerously irresponsible and disingenuous thing there is.

If you're uber-religious, fine.  You still can't claim to "know" everything because that would be claiming you are as knowledgeable about God as God is.  Are you ready to go there?

If you're an atheist, fine too.  You still can't claim to "know" everything because science hasn't solved all of the unknowns yet.

So, it looks like there's a BIG GAP in the middle where us stupid-ass humans really don't have ALL the answers.  So rather than expelling hundreds of cubic feet of wasted air and ear drum torturing, how about you just STFU and be happy to believe whatever it is you believe and let me get back to work.  Otherwise, you qualify as King Douche.

Pseudo Individuality

You got a raise or a nice tax refund.  You jump for joy and do your best end zone TD dance and almost throw your back out.  You start brainstorming what you're going to spend it on.  I can go ahead and tell you what you're statistically most likely to do with it...

• Buy a red, blue, black or silver Chevy Camaro, Ford Mustang or Dodge Challenger
• Buy a "custom" Harley knock-off, with the standard-issue leather chaps, boots, vest, and tired-ass Nazi battle helmet.
• Buy a set of Celtic style tattoos
• Get a big screen TV
• Get your teeth whitened or a set of Invisaligns
• Get a hair weave

Thirty years ago, you would have made an extra effort to NOT spend it on anything that was considered "popular".  That whole perspective of being "different", "unique", and (dare I say) "innovative" is dead and buried.  Back then, you built a chopper from spare parts and it was your own creation.  I know because I grew up surrounded by them.  Today you buy them off a web site and click the little scroller to cycle through the options and styles.  Progress isn't really progress, it's douche-gress.

War Buff Blabbering

You're at a party or bar or around a bunch of guys you're trying to impress.  You start off a sentence with "what they should do in Iran is..." and tack on some verbage about sending in SEAL teams, dropping bombs, and killing massive numbers of people to prove we are the biggest and baddest-ass nation on Earth. After all, that's what Jesus would do, right?  You start talking about mechanical terms and you feel a strange sexual arousal while spatting off names of tanks, planes, ships, guns, and high tech weaponry.

Then someone asks you: "Hey.  Have you been in a war?  Ever kill anyone?"  You stammer and stumble a bit, hem and haw, and try reinforcing yourself against the blinding punches to your brain by describing how many of your friends and family are in the military.  But the question is repeated, and you still can't answer it correctly.  You have stepped into the Douche zone.

Read More

Windows 8 Task Manager

The new Task Manager application in Windows 8 isn't a radically new thing, but it certainly has been overhauled and polished up quite a bit.  Some parts of it, such as the Details panel (figure 5), will look familiar.  Some are new, such as Application History (figure 3)

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Read More