Windows Tech Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Friday, 30 September 2011

Swallowing Without Looking

Posted on 03:00 by Unknown

Sometimes I have to stop and question things that just don't quite seem right.  Maybe it's because I'm a big fan of George Carlin, Frank Zappa and others that never made a habit of accepting things blindly.

Case in point: Light Rail safety PSA campaign

The ads say "Light rail safety.  It begins with you."

This is wrong.  There is no logic in this statement whatsoever.  None.  Zero.  It's completely wrong and stupid.  The fact that people accept this statement without question, is one thing. But when people take it up on defensive posture during a discussion, well, that's just shitheaded.

Is it bad to emphasize safety?  No.

Is it bad to suggest pedestrians and drivers be safe around light rail systems?  No.

So what's wrong?

Here's what's wrong:  Light rail safety, like any infrastructure-oriented safety, doesn't "begin" with "you".  It begins with a safe design.

PERIOD.

light-rail-transit-system-richmond

Consider this:  If a system makes it not only possible, but probable, even predictably probable, for a categorical "accident" to occur, it has failed the safe design test.  FAILED.  This is one of the basic tenants of statistical analysis.  You're supposed to strive to minimize risk and failure in any system that adds risk to human life or well-being.  A basic statistician can calculate the relative risk deviations between two alternative design patterns.  A categorical failure would be a pedestrian interaction with the movement of the train car, or that between a personal or commercial vehicle and a train car.

Typically, the approach would be to identify parallel "baseline" systems to assess comparative risk and probability.  This isn't the first light rail system to be built in a U.S. city.  There are likely many "lessons learned" that could provide excellent baselines on which to determine the relative deviations and risks.  Damn.  I think that's also referred to as "learning from past experience".

The next step would be to take that assessment data and work to mitigate those risks to "close the gap" between the proposed design and other existing designs.  For example, to mitigate the risk of a collision between ground-dwelling pedestrians, cars, trucks, motorcycles and buses, you could raise the light rail tracks above ground to provide isolation.  Gee.  Sound familiar to any of you folks in Chicago?  This also serves another, equally important goal: isolating new systems from interfering with existing systems.

The culprit here is obvious: Funding.  But funding was actually a symptom of politics, as it usually is.  In this case, the other near-by cities backed off from committing to the project because of political pressure to cut spending across the board in a Recession.  So Norfolk went for it alone.  Because they couldn't afford the added costs of raising the tracks from end-to-end, we have a system that is less than ideal, but workable.  Risky, but predictably so, at least somewhat.

Would an elevated track design be the perfect solution? Nothing is perfect.  However, such a design change would arguably provide risk mitigation for at least two of the identified categorical risks: interference and collision.  These two risks are very high on the probability score for causing injury or death, which are bad (at least, that's what I was told).

They knew of these risks well in advance.  Otherwise, how would they have scripted and produced the ads to convey this message a year ahead of the grand opening?

When someone or some people collectively agree to proceed with something that has known dangers, we call it "acceptable risk".  Drug companies, tobacco companies and car manufacturers operate on acceptable risk every second of every day.  So do pilots, divers, EOD technicians, and even school teachers.  You do it to: every time you drive your car, motorcycle or truck.

There are no "sort of" grades here though.  A logical statement is a logical statement - or it isn't.  Think of commercial aircraft: What if the airlines said that safety of the aircraft in flight "begins with YOU", rather than with a safe aircraft, trained crew and reliable parts?  Still make sense to you?  How about, "safety in the operating room - begins with YOU", rather than a skilled surgeon and staff, and sterile equipment?  That would be stupid.  So is arguing that "we" as riders are primarily responsible for the safety of the light rail system.  Stop letting these D-grade marketing ad campaign morons off the hook.  I'm convinced the ads are dumb is because Norfolk couldn't afford to pay for a better Advertising firm, which I can understand.

Am I overreacting?  Maybe.  Or is it shining a light on yet another whittling away at our collective sense of acceptable logic?  Remember when you were five or six, and you questioned everything you saw or heard?  Why did you stop?  Why do we all stop?

How then, should the PSA have been worded?

"Light rail safety.  It's important for all of us."

Read More
Posted in advertising, people, safety, society, stupidity, transportation | No comments

Thursday, 29 September 2011

The Zen of Systems Automation

Posted on 17:29 by Unknown

Level 1 - Writing scripts, hacking code, building your own solutions

Level 2 - Finding existing scripts, code, solutions and leveraging them with a little effort

Level 3 - Leveraging built-in functionality without having to write any custom additions

Level 4 - Systems run themselves.  You drink beer and focus on other things

Read More
Posted in automation, network administration, systems architecture, thoughts | No comments

Interaction is Highly Overrated

Posted on 16:58 by Unknown

Compact rambling edition:  As in, compact text format.  Tough on the eyes?  Suck it up.  Some people don't have a computer.  Some people don't have eyes.  Some don't even have fingers.  Let's see you complain now.  I didn't think so.

So much for part 1 of my grand "experiment".  Not even one response to the questions on my quasi exam?  Geez.  I expected at least one reply.  Just for that, I'm not posting the answers.  You guys can figure it out using Google.  No more of those.  From now on: random stupidity.  Actually, I can probably chock that up to making it too long for most people to even read the whole stupid thing.  Still with me?  Just checking.  As I've mentioned before, this is wearing on me, and my Dec 24 date is still on track at this point.  At my current rate of descent, remaining fuel, and distance to that target, I should just about make it before completely burning out.  Buckshot doesn't go as far as a single projectile, just as scattered thoughts don't travel as far as the focused.  I'm looking upon this as retirement.  Still there?  Ok.  Four years of rambling incessantly is losing its luster.  Some days I get a spark to ramble upon; other days I'm inspired by something from work, and some days it's just a brain dump of utter stupidity.  I mean, as much as I truly miss Ze Frank's "Show", I can appreciate how much he worked on that and why it only lasted one year. No, I haven't been drinking, and no, I haven't gone without sleep.  I'm actually amazingly lucid right now, even though it's been a long day within a very long and crazy work week. 

I'm looking forward to this weekend.  Tomorrow: Friday, is supposed to be the last Summer-like day of the year, getting once again into the 80's.  Saturday will only reach the mid 60's and be windy.  Fall is here.  In Virginia that lasts about a week and then we break out the coats and put the shorts in the bottom drawer for next year.  The only major thing I'm anticipating now is starting my treatments for skin cancer.  Don't freak, I don't have full-blown cancer yet.  It's pre-cancer treatment, so that makes it pre-chemo?  Anyhow, not a surprise given how much I live outdoors and with freckled skin, well, you know.  Anyhow, October is going to be interesting.  I can't complain since several of my friends have had or have full-blown Cancer and are soldering on through it bravely.  No whining here.  So far, so good.  I've always said that God may love me, but he/she sure doesn't like me.  Not letting me croak yet, more punishment to dish out to me yet I'm sure.  I'm actually more looking forward to the grand opening of the new Yard House pub in Virginia Beach in mid November.  That will make for two Christmas's this year.

Read More
Posted in blogs, bongloads, thoughts | No comments

Wednesday, 28 September 2011

Testing. Testing. Testicles?

Posted on 17:39 by Unknown

I'm guessing that got your attention.  I'm going to be doing an experiment.  I do lots of experiments, experimentally speaking of course.  What I'm doing now is trying on different topics and subject matter to see how traffic responds.  I've given up asking for input, nobody responds.  At least not with anything specific or clarifying in any way.  So this ship is still adrift without a rudder.  The two recent posts on Autodesk network deployments are a part of this experiment.

Here's what I'm seeing so far:

The 5 most popular articles I've posted thus far, based on unique visits between January 1, 2011 and September 28, 2011 are...

Title Hits
Home Page (changes often) 3,624
Windows 7, MSG.exe and Group Policy Preferences 3,120
Enabling Windows 7 Remote Management via Group Policy 1,808
What does the AutoCAD PURGE Command Do? 1,779
Packaging Autodesk DWG TrueView 2011 1,449
Packaging & Deployment of AutoCAD 2011 Products with System Center Configuration Manager 2007 816

Based on these numbers, I could draw one of two conclusions:

A. Windows 7 topics are the most popular ... or ...

B. Most of you just read whatever happens to be on my home page

Ugh.  Face-palm.  I'm talking nonsense to myself about nonsensicle nonsense.  The irony for me is that I receive a lot of e-mail asking for various things, mostly related to AutoCAD or Autodesk product issues, especially deployments and licensing services, etc.  I'd like to ablige with more focused content, but I need feedback from YOU to point me in the right direction.

Read More
Posted in articles, blogs, technology | No comments

Tuesday, 27 September 2011

Autodesk Network Deployment Strategies

Posted on 19:00 by Unknown

This is going to be sort of an extension of yesterday's post and on some of the topics covered in my book "The AutoCAD Network Administrator's Bible".  Mainly: how to unleash an Autodesk network deployment installation on your network with some logical and strategic efficiency regarding traffic isolation.

If you've ever taken a certification exam, this may all seem very familiar.

Background

Let's start with a model:  Fictional Corporation

New York, NY - is the main data center for the company.  The data center is state of the art with blade servers, SAN device arrays, and virtualized servers and virtual data center switches.  While being the largest office in the company, there are no AutoCAD users in this office, at present.  However, the company IT department creates and maintains all software distribution resources for the company.  They build the AutoCAD network deployment and host it (initially) in the NY data center.

Chicago, IL - is the second largest office in the company, but has the largest concentration of AutoCAD users in the company.  The connection between NY and Chicago uses multiple/redundant T-1 connections.

Washington, DC - is the third largest office, with the fewest AutoCAD users.  The connection link between NY and DC is fractional T-1.  Not bad, and not unreliable, but not as fast as the NY-Chicago link

Virginia Beach, VA - is the smallest office with the second largest group of AutoCAD users.  The link between NY-VB is fractional T-1, about the same performance characteristics as NY-DC.

The IT department utilizes Microsoft System Center Configuration Manager 2007 to deploy software, updates, collect inventory data, as well as uses it for provisioning new and refreshed computers.  There are primary site servers in Chicago and Washington DC.  Virginia Beach has a seconary site server.  All four site servers are also distribution points.

The file, print, and Configuration Manager site servers in the remote offices are physical machines.  The servers in NY are virtual.

Situation

All computers in the company run Windows 7 Enterprise Edition, Service Pack 1.  All servers are running Windows Server 2008 or 2008 R2.  The IT department has installed a FlexLM(R) license server in New York and obtained a valid license file from Autodesk.  They have configured the license server and verified it is operating normally.

The IT department creates the first AutoCAD network deployment share on a server in the NY data center.  They are aware of the deployment caveates for .NET Framework 4.0 and have already packaged the AutoCAD DirectX(R) component installer as an .MSI. 

Using Configuration Manager (aka "SCCM"), they deploy .NET Framework 4.0 to all computers in the company successfully.  They also deploy the DirectX(R) custom installer successfully. They then deploy a few test clients in the NY office using SCCM successfully.  Everything so far looks good.

Within SCCM they assign additional distribution point servers for the AutoCAD deployment package, one for each remote office.  They create the necessary collections and add direct memberships for clients in each remote office to a corresponding office-related collection and assign the advertisement.

The IT department runs server data backups over the WAN links to the NY data center for archival between midnight and 2AM ET (1AM Chicago time).  Client computers are schedule to run disk defrag, and anti-virus scans between 2AM and 4AM local time.  Tests show that the AutoCAD deployment takes roughly 40 minutes to install on a full T-1 connection, and 60 minutes on a fractional T-1 connection.

Few, if any, of the remote office clients successfully install.  Most return an error that the package timed out.

Question 1: What Happened?

What might have caused the remote office clients to fail the installation attempt when the clients in the New York office completed the installation just fine?  Was it...

  1. The Package did not finish replicating to the remote office distribution point servers.
  2. The network links might have been saturated with concurrent traffic during the deployment.
  3. The replicated package files contained identical deployment .INI content, so the clients attempted to install from the New York server share.
  4. Answers 1 and 2
  5. Answers 2 and 3
  6. All of the Above
  7. None of the Above

The answer is (definitely) 3 but could also be 2, so the best answer is 5.

Question 2: How to Fix This:

When you run an installation from the network deployment share, the process refers to the DEPLOYMENT_LOCATION key in the .INI file.  So, what's the best way to address this?

A. Open the deployment .INI on each SCCM package share and edit the DEPLOYMENT_LOCATION value to refer to the local share UNC path.

B. Build each deployment "on" a server in each remote office, then create a SCCM package and program that refers to the UNC as a distribution share.

C. Build each deployment "on" a server in each remote office, in a separate folder create a .bat or .cmd script that references the setup command for that server.  Create a SCCM package and program that points to that script.

Best Answer?  ____

FlexLM License Servers

After sorting out their deployment issues, all clients are working fine and obtaining licenses from the license server as expected.  The IT department decides they want to add a little redundancy by implementing two more FlexLM(R) license servers in a Distributed configuration.  They provision a license server in Chicago and another in Washington DC. 

The clients were originally installed using a system environment variable to assign the FlexLM(R) server setting.  Now they want to reconfigure the Chicago users to point to their own license server first, then the New York server, followed by the DC server.  The DC users are to be configured so they point to their license server first, then New York, followed by Chicago.  Lastly, the Virginia Beach users should point to DC, then NY, and then Chicago.

What's the Easiest way to accomplish this change?

A. Modify each deployment using the deployment utility "Modify Deployment" link, and enter new FlexLM server information, then re-deploy the installations to all clients for each site.

B. Create a SCCM package and program that executes a script to configure the system environment variable to suit each location.  Target the clients using collections based on site assignment.

C. Create four Group Policy Objects with a Group Policy Preference setting to replace the system environment variable value, link the GPO to the Active Directory OU for each site.

Best Answer?  _____

Read More
Posted in autocad, autodesk, deployment, network administration, software deployment, systems architecture, technology | No comments

Slow Autodesk Network Deployments?

Posted on 17:00 by Unknown

One advantage of being a "consultant" is getting to peek into a variety of environments, cultures, methodologies, and whatnot.  One thing I see fairly often that seems to warrant some mention is slow performance over network pathways.  A cursory search on Google reveals that there are plenty of articles, blog posts and tweets regarding slow "deployment creation", it's tough to find anything really focusing on the execution side: deploying the installation from the share to the clients.

fotolia_260932_XS

The potential points of trouble or failure in a typical LAN or WAN environment are numerous.  From client hardware and software, to client configuration settings, to physical wiring, switches, hubs, routers, wireless equipment, wireless configuration settings, server hardware, server software, server configuration settings, scheduled backups, scheduled anti-virus scans, unpredicted end-user activity, power faults, wireless interference, and layer on top of all this the issues incurred in virtual data center environments.  These are some of the aspects and any one of which (or combination of several) that can cause performance drag or outright failure.  The more you dig into the world of network engineering, the more you can appreciate what a network engineer deals with.

So, if you're Autodesk product network deployments are taking longer than they should to deploy, here are some things to look at:

Network Site Link Speeds

If your employer is large enough to have a dedicated "network admin", consult him/her for link speeds between points of deployment (server shares) and end users (desktop and laptop computers).  Find out how many hops are involved.  What the switches and routers are like.  What limitations they're aware of.  I recommend doing this BEFORE you even attempt to build network deployment shares (referenced in my book.  shameless plug, I know)  Basically, you always want to keep as little time, distance and latency as possible between the installation source and the installation target.  This is irrespective of doing it manually, via scripts, group policy or management products like Configuration Manager.

NIC Configuration Settings

Verify the Network Adapter configuration settings with your network administrator.  I've seen plenty of situations where everyone assumed it was automatically set to the correct configuration, when it was anything but.  Sometimes atypical network equipment configurations require atypical client configurations to suit.  Even if you are absolutely, positively convinced that all of your clients are using identical and correct network settings, check them again, just to be sure.

Concurrent Utilitization: Server

If your deployment share resides on a file server, or a print server, or an application server (web, database, etc.), I would STRONGLY recommend you consult your server administrators to setup some performance monitoring to measure and verify the loads placed on each server.  If one role or function is hogging the resources (CPU time, memory, disk I/O, NIC throughput, etc.) consider moving it to another server.

If concurrent roles or functions are not an issue, check to see when system and file backups are scheduled to run.  Do your best to avoid scheduling your network deployments during system backups, anti-virus scans, or scheduled maintenance.  If your servers are virtualized, and your server admins ocassionally move them from one physical host to another (or SAN storage attachments, etc.) it's important to coordinate your activities to avoid problems.

Talk to your department coordinators or "power users" also.  Make sure they don't have any tasks they run during certain hours to back-up their project files, or perform operations that directly tax the server or its resources.  Copying a ton of large files can greatly impact network performance if the server is not configured to address that usage ahead of time.

Always always always check the event logs for any sign of potential issues.

Concurrent Utilitization: Network

If the server is not being taxed, you should take a careful look at what's going over the network segments.  Between the clients and the switch or gateway.  Between the switch or gateway and other routers, and between the other routers back to the servers.  There are lots of ways to do this and it's important to consult and coordinate with your network admins to do this effectively.  In many cases they can help identify bottlenecks caused by two major traffic activities that can be separated to avoid conflict.

Client Integrity

Check for available/free disk space on the target hard drive volume.  Check for errors and warnings in the client event logs.  Is the client getting frequent anti-virus quarantine events?  Are installed applications causing problems?  Be careful of applications that want to continue running in the background, especially when the client is tight on physical memory.  If the computer is being used heavily, consider upgrading the hardware or installing a separate physical hard drive to isolate I/O tasking.  The list here goes on and on, of course.

Client Activity

Are users performing CPU or disk-intensive activities?  Rendering large models, video processing, audio editing, etc.

More

Oh yes. There's more.  MUCH more.  I haven't (and won't) go into the impacts of other key networking services like DNS, Kerberos, WINS, DHCP, encryption overhead, certificates, dual network interfaces, teaming, virtual switches, virtual NICs, or any of that stuff.  It's more than I feel up to blabbering about, but it's out there, waiting for your brain to absorb it all.

And Finally...

Before you jump into building your network deployment, especially if you're aiming for multiple servers across a WAN, it's important to gather as much information as possible about your network so you can plan your strategy correctly.  If you spent hours convincing your coworkers, management and customers/users that network deployments are the "way to go", don't you want to make sure it works as great as it possibly can?

Consult your network and server administrators.  Run tests to verify file copy speeds across all links you plan on using.  Run your tests over a month or at least a few weeks, at all times of day, all days of the week.  Record details of performance and identify patterns in best and worst results.  Pointing a finger at one of your network admins and blaming them for slow speeds is only going to piss them off and get you moved to the bottom of their list of things to take care of.  Having measurement data and engaging in a cooperative discussion will get you where you want to go with the least amount of pain and effort.  Be sure to bring donuts and tell lots of jokes too.  It never hurts.

Tools and Links

WindowsNetworking.com - Troubleshooting Network Issues

Advanced Network Adapter Troubleshooting for Windows Workstations

WireShark (the de facto diagnostic tool)

Network Monitor 3.4 for Windows 7, Vista, Server 2003, 2008, 2008 R2

Sysinternals Networking Utilities

Sysinternals Process Utilities

Books by Mark Minasi at Amazon

Network Diagnostics and Tracing in Windows 7

NETSH commands for Windows 7 and Windows Server 2008 R2

Read More
Posted in applications, autodesk, deployment, network administration, software deployment, systems architecture | No comments

Querying Services on Remote Computers

Posted on 15:10 by Unknown

I'm still amazed that so many up-and-coming admins and SE's knee-jerk to using a script to perform a task that is readily available from a command prompt.  In this case, the SC command.  The SC.exe command resides in the %WINDIR%\System32 folder on most Windows XP, Vista and Windows 7 systems (as well as Windows Server 2003, 2008 and 2008 R2).  It's also alive an well on Windows 8 (Dev Preview build, anyway), and I presume resting within Windows Server 8 as well (I haven't seen it yet).

The syntax is rather basic:

sc <server> <option> <parameters>

but most people use it for querying the local services state, as follows:

sc query

The flexibility comes with the "<server>" argument, which is the NetBIOS computer name (with preceeding \\), so to query a remote computer named DESKTOP1 over your network...

sc \\DESKTOP1 query

And just add a piped "| more" to pause screen-by-screen (or redirect into a file, etc.)

One short and simple command, instead of a bunch of VBScript or even a lengthy Powershell cmdlet.  Nothing wrong with those options, but it's nice to know there are other alternatives.

Remember: To break open this little nugget, open a CMD console and type "sc /?", press Enter and enjoy!

Read More
Posted in cmd, network administration, scripting, services, windows | No comments

Test ADO Connection using VBscript

Posted on 13:31 by Unknown
Quick ADO connection test using VBscript...

[code]

Const dsn = "{your connection string or DSN name here}"

On Error Resume Next
Set conn = CreateObject("ADODB.Connection")
conn.ConnectionTimeOut = 10 ' 10 second wait limit
conn.Open dsn

If err.Number = 0 Then
wscript.echo "CONNECTION: SUCCESS"
Else
wscript.echo "CONNECTION: FAILED"
End If

conn.Close
Set conn = Nothing
[/code]

Read More
Posted in databases, scripting, vbscript | No comments

10 Ways to Manage Windows Services

Posted on 04:26 by Unknown
  1. Services Console (services.msc)
  2. Command Line: sc.exe
  3. WMI / COM Script: VBscript, KiXtart, Javascript, Perl, etc.
  4. .NET Script: PowerShell
  5. WMI Class Provider: Win32_Service
  6. Group Policy Object
  7. Group Policy Preferences
  8. Utilities: PSService.exe (Sysinternals/Microsoft)
  9. .MSI installer
  10. .EXE application or installer
Read More
Posted in kixtart, network administration, powershell, scripting, services, vbscript, wmi | No comments

5 Ways to Read Windows Event Logs

Posted on 03:21 by Unknown
  1. Event Viewer application (eventvwr.msc or eventvwr.exe)
  2. Command Line: wevutil.exe
  3. WMI/COM Scripting: VBscript, KiXtart, Javascript, Perl, etc.
  4. .NET Scripting: PowerShell
  5. Collectors and Forwarders: wecutil.exe
Read More
Posted in events, network administration, powershell, scripting, vbscript, wmi | No comments

Monday, 26 September 2011

Automation Gyration

Posted on 17:45 by Unknown

I recently updated some information on my tabular matrix of "Windows 7 Automation Options" over at my other other other web site.  The goal of this matrix is to map out alternative ways to perform common administrative tasks and compare which is best for certain conditions or situations.  Let me know if you want something added or if you have a correction to offer.

Read More
Posted in automation, environment, group policy, network administration, registry, scripting, services, windows 7 | No comments

11 Ways to Manipulate the Windows Registry

Posted on 17:35 by Unknown
  • Direct via REGEDIT
  • Command line using REG.exe
  • Import via .REG file (invokes REGEDIT)
  • COM Scripting: VBscript, KiXtart, Perl, Javascript, etc.
  • .NET Scripting: PowerShell
  • Group Policy
  • Group Policy Preferences
  • .MSI installer
  • .EXE application
  • Stream Interface: Java
  • Temp Labor:  Order Timmy to do it
Read More
Posted in network administration, operating systems, registry, windows | No comments

Sunday, 25 September 2011

Acad 2012 DirectX - The Final Chapter

Posted on 16:29 by Unknown

I know that I said I was done with this topic, but someone hit me up over the weekend with a desperate request for help and I couldn't say no.  As always, I prefer to share answers on the blog rather than by e-mail because it [A] helps more people at one time and [B] avoids repeating the same answer over and over.  This might go a bit deep, but hopefully it serves to help someone out there to get over this hump with a little less effort.

The Better Way

If you have InstallShield, here's how to do this in the simplest and most effective way:

  1. On a clean reference computer (virtual machine) install the Remote Repackager
  2. Start the Repackage Wizard and select "Snapshot" mode, using multiple steps
  3. When the capture is done, click Finish
  4. Copy the "DirectX" folder from the "3rd Party" sub-folder of your AutoCAD 2012 network deployment into the C:\Windows\Temp folder of the reference computer (making C:\Windows\Temp\DirectX)
  5. Open the folder and launch DXSETUP.exe and complete the process to "finish"
  6. Re-run the Repackage Wizard in snapshot mode to capture the delta state info
  7. Save the output to C:\Packages on the reference computer
  8. Copy the output up to your InstallShield developer share so you can edit it further

When you open it in Repackager, exclude all the junk that relates to "per-user" stores (HKCU, User Profile, etc.) and exclude anything not related to your DirectX installation (background scans, scheduler services, etc.)  Save the output to a new folder (e.g. "Project")

Open the .ism output from the "Project" folder in InstallShield Editor.

Set all the desired properties (title, subject, comment, etc.), there's a lot of stuff to manipulate, so unless you need all the nitty-gritty details I'll skip over them for now.

Build the project into an .MSI package

Run the MSI Validation and clean up any ICE references that matter (ignore ICE27, for example - but don't ignore ICE18, and so on).  Build again, and repeat the Validation until all is good.

You should now have a .MSI installer

TESTING

Once you have your shiney new .MSI installer, test test TEST TEST TEST TEST it until you feel good it's working like it should.  By TEST I mean install it on a new computer, along with .NET 4.0, and then target that computer with the AutoCAD 2012 network deployment using Configuration Manager 2007 or Altiris, etc.  If it works fine and the application launches without errors, you're good.  DO NOT - I REPEAT - DO NOT look at the Configuration Manager advertisement report for the "Success" and call it a "win".  That's NOT good enough.

DANGER ZONE

This is where we separate the men from the boys (or more apropos: we separate the daring idiots from those that prefer to keep their job).

WARNING: The rest of this article is UNSUPPORTED and potentially RISKY.  Always make a backup of your entire AutoCAD network deployment share before making any manual changes.  This information is NOT supported or condoned by Autodesk, its resellers or anyone on this planet.  I do not guarantee this will work for you and there is NO WARRANTY provided, either explicitly or implicitly, for any purpose or use whatsoever.  I accept NO LIABILITY or responsibility for any consequences that may arise from your use or adaptation of this information for any purposes.  In short: YOU ARE ON YOUR OWN - YOU ACCEPT ANY AND ALL RISK from this point on.  Results may vary.  Batteries not included.

Place the new Acad2012DX.msi file in a folder under your AutoCAD 2012 network deployment share.  You can drop it in the "DirectX" folder actually.

Open the deployment .INI file and locate the [DIRECTX] key.  It should look something like the example shown below.

[DIRECTX]
PLATFORM=ALL
PRODUCT_NAME=DirectX Runtime
EXE_PATH=3rdParty\DirectX\DXSETUP.exe
EXE_PARAM=/silent
IGNORE_FAILURE=YES
DISKCOST=50000000

Change the values beneath it to suit the new .MSI installer, as shown in the following EXAMPLE...

[DIRECTX]
PLATFORM=ALL
PRODUCT_NAME=DirectX Runtime
EXE_PATH=3rdParty\Directx\Acad2012DX.msi
EXE_PARAM=/quiet /norestart
LOG=%tmp%\Acad2012DX.log
IGNORE_FAILURE=YES

Save the file and test a deployment on a computer that has .NET 4.0 but has not had AutoCAD 2012 installed prior to your testing. 

NOTES

I have not provided any guidance for getting .NET 4.0 to install with the AutoCAD deployment bundle (via a Configuration Manager 2007 unattended deployment), because I feel it's bad to try to do it that way.  I recommend deploying .NET 4.0 as a separate package/advertisement, in advance of deploying AutoCAD 2012.  The only reason I bother with DirectX like this is because it's a custom DirectX installation (from Autodesk, not me), so it fits more logically with the AutoCAD deployment, than as some sort of general Windows platform update.  Basically, you would never deploy this without AutoCAD 2012, while .NET 4.0 on the other hand would be.

I hope this wraps this boring, ugly, depressing saga up with no hanging threads.

Drop a comment (reply) here if you have any helpful advice for making this work better/faster/easier than I've described.  We'd love to hear it.  I'd love to put the final nail in this coffin and move along actually.

Read More
Posted in | No comments

10 Easy Ways to Screw Up a Good Computer

Posted on 11:37 by Unknown
  1. Install too much crap on it
  2. Don't install a decent anti-virus product
  3. Never defragment the hard drive
  4. Never install updates and service packs
  5. Don't vacuum out the dust and dirt
  6. Let a lot of other people use your computer
  7. Never clean out the various "temp" garbage files
  8. Never reload it from what Dell/HP/BestBuy, etc. install on it
  9. Install one of those computer "fix-up" products advertised on TV
  10. Never seek education on how to use it more effectively
Read More
Posted in articles, computers | No comments

Saturday, 24 September 2011

College Degree vs. Cert vs. Experience

Posted on 09:26 by Unknown

At this point in 2011, the Information Technology field is doing very well. For whatever reason, the number of jobs in nearly all IT fields are more plentiful than they've been in almost four years.  Many businesses have finally come to the realization that cost-cutting is great, but not so much when applied to their own IT operations.  It's like tossing out dead weight from a moving train, and then starting to unbolt and discard the engine.  Someone finally says "Wait! This is not a good idea!", and they start working making sure the engine keeps working.  This is the phase we're in now.  Businesses are investing in IT to help leverage existing resources more thoroughly and find hidden nuggets to put to use.  We've all heard it for so long that it's become background noise, but it's actually happening, and not a minute too soon.

For this reason, there are now more jobs in the IT field than we've seen in quite a few years.  This is especially true in the U.S.  Not as many as there were heading up to the Recession, but better than any year since, for sure.  Way better.  As a result, a lot of kids are starting to take another look at the IT field as a career choice.

Ironically, part of what quelled interest in IT careers for most high schoolers between 2004 and 2008 was a media frenzy focusing on "outsourcing" to other countries.  U.S. kids would often tell their counselors and college recruiters that they didn't think the IT field was viable in the U.S. They would typically say it was because future jobs would be going to India, China and elsewhere.  That belief actually constrained future labor prospects for a few years to the point where many large corporations began ramping up their outsourcing to other countries to hedge their bets.  Belief often leads to perception, and perception guides action, as they say.

But that effort hasn't panned out so well for many companies, for a variety of reasons and unforeseen market changes.  Some aspects of IT have proven to work very well in a global labor market, while others work best when kept in house.  So far, anyway.  This is true for any company, in any country, not just in the U.S.  This has led to a recent increase in internal IT hiring within the U.S. and indeed in many other countries.  I'm speaking here mostly about the U.S. market, since that's what I'm most familiar with (if anything).

What to Do?

This is a topic (the headline of this post) that comes up quite often, especially coming from kids just about to leave High School.  I hear it from veterans about to part ways with the military after their term of service is about to end.  I hear it from people that work in other fields and want to try another option in life.  Those that are interested in pursuing a computer-related career of some sort, tend to ask the same batch of questions:

"Does a college degree help?"

"Should I get certifications first or after school? Instead of school?"

"Do certifications or school even help in the IT field?"

"Microsoft?  Apple?  Open Source?"

"What part of IT is the best to work in?"

Answering these questions is tough, because there are many variables.  The best answer is "it depends".  My colleagues will chuckle over that since they say it's the quintessential consultant response to every question...

"Dave, if I swallow a live hand grenade and jump into a raging arc furnace, will I survive?"

"It depends."

...and so on.

Anyhow, the significance of having a degree, a cert or years of experience, upon your career opportunities is somewhat like asking what attracts one person to another.  Some are looking for certain qualities or traits, while others have completely opposite preferences.  Cars, clothes, money, looks, height, race, religion, speaking accent, social life, hobbies, or sense of humor, honesty, confidence, vulnerability, and so on.  Then there's affluence and demographics.  Oh shit, this could go very deep and into an area I'm not qualified to speak about. (as if I'm qualified to speak about anything)

Basically, there is no ONE answer.  Here's why...

Environment Scale.

If you intend to work for a large corporate employer, things like college degree and certification might matter a lot.  In fact, they usually do.  Some will place more value on those two aspects of a potential hire than on past experience.  Others place more value on experience than on anything else.  And yet others place more value on "gut feeling" and "personality".  It depends on what that employer has in mind for what they're going to have you do (job role or job description).

Smaller employers (mom and pop up to medium sized businesses, even some non-profits) may focus more on experience alone.  Some may focus more on a degree and experience.  It varies.

Case 1: A large defense contractor wants to hire someone to work on a particular software-oriented weapons system for a large military customer. They interview two candidates:
Candidate A - has a Masters Degree in CS from a reputable university, and 5 years experience at a competing firm working on large software projects.  This candidate has little or no specific knowledge or experience with this particular weapons system, nor with the customer it relates to.
Candidate B - has no degree at all, but has 5 years of hands-on direct experience working on that very same weapons system for the same military customer.  This candidate demonstrates an articulate knowledge of the system and how to operate it, as well as as its shortcomings.
Guess which one will get hired?  Obviously, this is a ceterus parabus situation (where I'm leaving out that all other aspects/traits of the two candidates are otherwise equal).

And for another...

Case 2:  A small business needs to hire full-time "IT Manager" to oversee an existing team of four, handling everything IT-related internally, from hardware to software.  They interview two candidates:
Candidate A - has 5 years experience running a small help desk at another small business, mostly supporting desktops, laptops and printers.
Candidate B - has 5 years experience running a small help desk at another small business, mostly supporting desktops, laptops and printers, and has a BS degree in computer science from a respectable school.
Guess which one gets hired?

These are obviously just two possible situations out of an infinitely possible world.  Either of these two could include additional conditions that would flip the choices either way.

There are equal balances of pro and con aspects to working in either a large or small environment.  Where one side gains from Flexibility, the other gains in greater Resource Capacity.  Where one side suffers from Repetitiveness, the other suffers from (lack of) Budget.

Stability is a Myth.

Never assume that the size or history of a company is a solid indication of job stability.  I've seen dozens (yes, DOZENS) of examples where large, historied firms were merged or aquired, or suffered a major defeat (internally or from competitors) and crashed.  I've seen small shops be aquired by huge companies and I've seen big companies decide to eliminate entire functions from their business. 

Workers of any kind (IT or otherwise), tend to be viewed as "units of labor" at certain levels of business management.  The weapons against that are necessity and utility.  You have to make yourself necessary and of great benefit to the business.  Note those italicized words.

Being a fifth wheel offers little benefit and can easily be eliminated to cut costs.  Being the only wheel, or one of very few wheels, makes you more valuable, BUT: only if you accel at what you do.

For example, I worked for a company for about seven years, that had continuously grown at a stellar pace for almost thirty years.  I had a ton of stock options waiting to fully vest and received regular raises and bonuses every year based on my performance.  Everything about that company was maturing steadily and the quality of hires was improving every day.  It seemed like the place where I would advance into a management role and retire from some day.

Then the CEO decided that he was going to retire, but instead of handing the reigns to the EVP, he was selling it to two companies and splitting it in half.  In a few weeks my stock options were nullified and my job was reduced to almost menial labor with almost no management direction at all. (even worse, I was being directed by two managers that hated each other and given conflicting orders, with HR doing nothing to resolve the matter).  My potential retirement investment portfolio dropped roughly $40 in a single day as my stock options turned to dust.  The fine print legal terms did not help us at all either, we were sitting ducks as a result of one man pulling the plug and ejecting with the only parachute.

In short: what seemed like a great future, suddenly turned into a cesspool.  The staff abandoned their posts day by day until I was the LAST person in my group left.  It was depressing.  Enough of that - let's move along...

Colleagues of mine at other major corporations have been laid off due to cost cutting efforts.  Others were laid off when their small business employers went under.  There are no garantees.  Nothing is for certain.  Even a lengthy history of strong results is no guarantee.  Ask anyone at RIM, Nokia, Cisco, Nortel, Motorola or Sun Microsystems.  Ask anyone at Microsoft from back in 2009. 

Here's the basic run-down:  small employers tend to have small lay-offs.  Big employers tend to have big lay-offs.

As I already said: The best defense against instability is to make yourself more valuable to the business.  Be careful:  Being valuable to the IT operation is NOT the same as being valuable to the business.  Remember that.

IT Roles Matter.

It also matters what particular aspect of "IT" you want to work in.  Tier-1/Help Desk? Server Administrator?  Software Engineer? Systems Architect?  Database Administrator?  CTO?  CIO?  Maybe you really want to work in content creation, such as multimedia production, or video services.  Each of these has its own unique needs, and its own unique focus on skills, credentials and experience.

As for the question "What part of IT is best to work in?", that is a very tricky question.  What is "best"?  Does "best" mean:

  • Higher paying?
  • More job opportunities in more places?
  • More flexibility?
  • More fun?
  • More opportunities to grow and advance?
  • Greater stability and security of employment?

You might find a field that pays more than another field, but ends up being boring or frustrating for you.  You may find a field that's fun and exciting but doesn't pay enough to live on.  You may find a position that is exciting and pays well, but ends up going nowhere and becomes a repetitive drag.

Some questions career counselors (specializing in IT) might ask:

  • Do you prefer creativity and flexibility or the challenge of solving complex problems more?
  • Do you prefer isolation and privacy or socializing and team environments?
  • Do you prefer an office or traveling, or working from home?
  • Do you REALLY want this or are you looking for a bigger pay check?
  • Do you prefer math problems or drawing pictures and diagrams more?
  • Do you prefer taking things apart and tinkering or using a mouse and keyboard?
  • Do you find massive scale complexity to be fascinating or dull?

How you tend to answer these questions might help guide you towards one aspect of IT or another.  Assembling servers and server racks, SAN installations, network routers and switches, running fiber, setting up wireless networks, encryption and authentication, firewalls and filtering, intrusion detection and prevention, designing software user interfaces, animation production, video content and production services, 3D engineering and design (CAD/CAM), software engineering, systems architecture, process automation, protocols APIs and ASICs, database administration, database engineering, business information modeling, process simulation and modeling, the list goes on and on and on. 

Each of these tends to favor certain personality traits over others.  I would provide some generalizations but I'm sure that would piss off quite a few people (haw haw), so I'll let you explore that aspect yourself.  Let's just say that IT functions that involve more isolated time tend to attract more isolate personality types, and the ones that involve more social interaction tend to attract the more socially interactable types.  Let's just say.

Most IT jobs are in an office with little travel, at least not enough to involve airports.  But there are plenty that involve some or even extensive travel.  For some that is exciting stuff.  For others that's a major drag.  You need to decide which avenue suits you best and be ready to answer that question during an interview.

Interviewer: "This job may involve extensive travel.  Roughly 75 percent of your time will be on the road or in the air, and you'll be going between the (U.S.) coasts and occassionally to Europe.  Do you have a problem with that?"

You: _____

Investigate.

Once you figure out what general field of IT you want to get involved with, find people that work in that particular field.  Don't ask your friend, who happens to be a DBA, what he/she thinks would be best for you to pursue a job as a Software Engineer or Technical Manager.  At least, not unless he/she has plenty of experience doing exactly that.  One thing you will find is that each vertical segment of the IT world has different views, opinions and perspectives on themselves than they have on other vertical segments.  If you want to be a Systems Engineer ask a Systems Engineer what it involves.  Better yet: ask three or more.

Figure out where you want to work, or what field of work, and then investigate what that environment wants in their employees. If that field or employer tends to prefer a particular college degree, or set of certifications, that should give you a clear target to aim for. Experience is a little tougher since you can't just sign up to get that. It comes from doing hands-on work and building a trail of accomplishments you can refer back to.

It's a big, complicated field of work.  It's a complicated thing to figure out too.

Confused?  Welcome to the party.

Read More
Posted in business, career, employment, jobs, management, technology | No comments

Self-Review Time

Posted on 06:43 by Unknown

Every so often, I will go back through some older blog posts and read them.  I usually cringe in horror.  Today is no different.  I realized how often I repeat myself, or re-introduce my background, each time I begin a particular subject dissection.  I promise to stop doing that.

FEEDBACK

Looking at the stats for my blog, it shows that roughly 25% of you are repeat visitors (thank you!!!!).  This begs the question: What topics or subject matter would you like me to focus on in future articles / posts? 

Post a reply to suggest some topics?

Read More
Posted in blogs, thoughts | No comments

Thursday, 22 September 2011

A Friday Mini Braindump

Posted on 21:40 by Unknown

This is a bit rambling, but hopefully worth your while...

I've been in training all week learning AdminStudio and InstallShield.  During that same time, work has not stopped or hibernated, and house chores haven't let up (my wife is hundreds of miles away visiting family right now), so my brain is a bit frazzled and woozy.

DirectX + AutoCAD 2012 + Configuration Manager = who cares?

During this same week I received several emails relating to my blog posts regarding the repackaging of DirectX for deploying AutoCAD 2012 via Configuration Manager.  That sentence is a ****ing mouthful.

I have already posted several articles dealing with this subject, and even included it in my book.  The recent inquiries have been about how to repackage the components for silent installation using something other than Wise Package Studio.  I ran through a few tests using InstallShield 2011 and it works as well (albeit using a somewhat more verbose process), and even toyed with merging the results back into the AutoCAD 2012 network deployment by way of editing the .INI file to point the [DIRECTX] sequence to use the new .MSI. (WARNING: this practice is completely unsupported by Autodesk, so if you pursue that, you're on your own.  Don't call me).

Then it dawned on me: I just don't give a shit about this topic anymore.  Maybe I'm getting older?  I'm just tired of making the same Band-Aid for the same mess; a mess I didn't create.

Wise Package Studio vs. InstallShield / AdminStudio

On a side note: I received some rather interesting responses about my comments regarding Wise being dumped by Symantec and why I feel InstallShield is a "better way to go".

Here's why:

  1. Upgrades to Wise Package Studio, since 6.x, have been minimal.  It's hard for even (former Wise/Altiris/Symantec) engineers to argue that 8.0 is nothing more than 7.0 SP4.  Even the community forums are rife with comments that indicate the future is gloomy for that product line.
  2. http://www.symantec.com/connect/forums/wps-80-vs-adminstudio
  3. My discussions with several Symantec employees at TechEd 2011 made it clear to me that even they do not know whether WPS has any future.
  4. Compare this http://www.flexerasoftware.com/products/installshield/top-reasons.htm with navigating the Symantec web site and trying to find a CLEAR link to WPS anymore.  They have been steadily burying it as time passes.  Don't believe me?  Check this out: http://www.symantec.com/business/products/allproducts.jsp  (press CTRL+F and enter "wise" and see how many matches it finds)

Wise is dead.  It just doesn't know it yet.  What a shame too.  It was once such a cool product.

Sometimes Reality Hurts

The painful reality of working in the IT field is this:

Everything you accomplish in the line of your IT work, and I mean EVERYTHING, will be gone and forgotten in ten to twenty years.

Your ancestors made furniture, built houses, roads and bridges, constructed buildings, and railroads.  We move bits around.  We can still find their furniture, their houses, drive on their roads and bridges, visit their buildings and ride their railroads.  You don't think your network, servers and software will vanish?  Ask the folks who built Windows 3.1 and the folks who worked at Sun Microsystems in the 1990's.

The reality is that no matter how important we think we are, none of our accomplishments will last as long as that hand-carved wooden rocking chair.  Those stone-laid Roman highways are a bitch, aren't they?

Feeling happier now?  :)

Sometimes Reality Feels Good

My son is 12.  He's been playing guitar for several years, only one of which did he take lessons.  The rest of his learning has been self-driven and via Google and various tab sites.  He averages roughly one new song per week.  He just picks something that catches his ear and he dives into learning how to play it.  It's amazing.  I can listen to him play for hours.

When I was 12 I had a bicycle and a TV with 3 local channels of 1960's re-runs and news.  Compared to today, that was like living in the Australian outback, but that was in Virginia in the 1970's.  For all the new inventions and distractions and the loss of naiveté of our modern world, seeing kids push themselves to do cool things gives me a good feeling that there's still hope.

Battery Life

During the power outage after Hurricane Irene last month, I started thinking about how long my various gadgets last when they're just sitting idle and not being used.  I decided to do my own experiment:

Google Chromebook CR-48 = 1.5 days

iPod Touch v1 = 2 days

Blackberry Tour 9630 = 2.5 days

Kindle Wi-Fi 3.0 = 7.5 days

The main difference, besides the construction and capacity of each battery, is really in how the firmware and software are devised to maximize (or not) the battery life.  Clearly we have not progressed very far with commercial battery technology in a long, long time.  We're just getting better at optimizing utilization of the technology we've had for so long.

I'm fried - enjoy your Friday (and your weekend!) - Dave

Read More
Posted in autocad, autodesk, directx, installation, marketing, network administration, packaging, software deployment, software packaging, technology, wise | No comments

Wednesday, 21 September 2011

What Makes a Great IT Professional

Posted on 17:23 by Unknown

This is purely anecdotal crap from the tip of my pointy head.  I've seen many lists of "top 10" skills or aspects, etc., but this is MY list, so I'm applying my own perspective.  This is all shaped by twenty-plus years of working in software development, infrastructure and server support, consulting, and so on.  None of these attributes alone is a reason to hire or not hire someone.  It's a cumulative score and everyone is different.  Quite often we compensate a low score with another higher score and it all evens out.  Or it may be that one major low score is enough to kill the prospect entirely.  I'm sure I've left some things out, and could have likely chosen better names for these "attributes" (even a better column heading than "attribute"), but it's a start.

Rank Attribute Explanation
1 Eagerness Energy is key in the IT field.  I don't need people that look at the clock more than at their task.  I have to feel a sense of enthusiasm for the job.  Eagerness is a key aspect of enthusiasm.
2 Humility No one is an expert at everything. Even for the few skills we feel confident about, there are plenty of people in the world who know more and perform them better.  Experts are easy to find.  People who understand how to fit into a team and work well with others makes the optimal capability for any operation.  Understanding that what we do in IT is not THE most important thing in this world is part of that.  Having perspective of ourselves, our role in the workplace, our function as a group, and how it fits with life in general are all components of humility.

There's nothing wrong with having confidence.  It's important to be able to explain your accomplishments and what they mean/meant to your business and your customers.  But bravado and egotistical mannerisms are a major turn-off to interviewers and employers.  Those traits almost always create friction with coworkers and are bad for a team environment.
3 Current Skills This dovetails onto "eagerness".  If at least a few of your IT skills are current, it shows eagerness and determination to improve yourself.  How can anyone expect you to help improve my business if you can't show me that you even want to improve yourself?  Don't tell me about Novell Netware, MS-DOS and WordPerfect.  Don't even tell me about LANDesk either.  Windows 7, Office 2010, System Center, Active Directory, Exchange 2010, VMware vSphere, Hyper-V, etc.  Get those on your resume and be able to back them up within a detailed discussion.

I ranked this above experience because many of us don't have the luxury of getting hands-on experience with the newest toys while at our day jobs. Many of us have had to go it alone, at home, into the late hours of night and on weekends, just to keep up with this fast-moving field. Such effort demonstrates eagerness and determination.
4 A Sense of Humor IT operates in groups and teams.  You have to be able to meld with a wide variety of personalities.  From prudish asswipes that never smile, to goofballs that annoy the shit out of everyone around them.  From lazy to driven.  From opinionated to ambiguous.  The more adaptable you are, the more possibilities exist for putting your skills to use.  Having a sense of humor is tantamount to being adaptable.  Let's face it: Nobody wants to work with people that can't smile or laugh.
5 Experience School is great.  Self-study is great.  But having some real hands-on experience in a business environment adds up to more than anything else.  School cannot teach a CS major how to effectively navigate the terrain of business politics, office culture, vendor relations, shifting business requirements, mergers and acquisitions, and the impact of paid training and bonuses.  Those aspects are powerful forces in the shaping of any solid professional.

I ranked this below having a sense of humor because it's easier to find experienced people than people with a good sense of humor.
6 Business Acumen IT serves one purpose only: supporting business operations.  Period.  Even if your business is IT, someone is doing the bookkeeping.  Someone is knocking on doors and getting contracts.  Someone is taking care of legal matters.  Most of those functions CAN be accomplished without an IT department.  Inefficient, yes.  But they can be done.  IT should make them more efficient and more productive.  IT should lower operating costs, provide advantages over competing businesses, and provide a safety net to prevent catastrophic loss of data.  The better an IT professional understands what the business operation needs and WANTS, the better prepared you will be to work together.  Adversarial IT-vs.-Business environments NEVER work out. Every one of those I've encountered has ended in failure.
7 Team Focus I'm not talking about meetings or metrics or reports.  I'm talking about sharing credit for successes and accepting blame for failures.  IT professionals who horde their knowledge and don't share it with their peers are bad for team morale and horrifically bad for an efficient and robust business operation. 
8 Appearance Dress professionally.  At least until you've been told by your employer that you can tone it down later on.  But don't show up for an interview with your hair messy, dirty or wrinkled clothes, worn out shoes (or flip-flops).  That shit is for fast food and gas station jobs.  I totally agree with Neil Patel that dressing sharp creates a powerful impression on employers and customers.  This goes along with Neil's "Lessons Learned from Running a Consulting Company" (reason no. 4)

On a subjective/personal note: I despise IT folks wearing vendor branding and logo clothing.  Don't be an advertising bitch unless they're paying to do it (and if they're paying you, don't ask me to hire you anyway).

As important as appearance is SMELL and BODY LANGUAGE.  If you don't bathe often or use deodorant you're going to offend other employees and that destroys a team environment.  Business does not like anything that destroys or impedes an efficient work operation.  Being less offensive is important to the eyes and the nose.
9 Cohesiveness Strive to get along with your teammates.  Avoid divisive or hot-button topics (religion, politics, etc.).  Make friends, not enemies.  Avoid drama. Keep your personal life personal.  Don't be an introverted paranoid basket case, but be sparing in volunteering your views and stories of personal adventures/mishaps.
10 Be Flexible Don't let your official job description box you in.  The person that looks for opportunities to do more and learn new skills is a powerful resource that adds value.  Higher value equates to pay raises, bonuses, training opportunities, and other perks.  Even if you have no desire to move up within your current organization, flexibility allows you to gather more skills and experience and demonstrates eagerness that your next employer will value.

Summary

If "fitting in" and working within a team environment aren't your cup of tea: Don't work in the IT field.  Find something more complimentary of your preferences to work alone or in a different field entirely.  The IT field ranges from small shops with one or two technicians, to freelance consultants who often work alone, all the way to larger corporate shops with dozens or hundreds of engineers, technicians, administrators, managers, architects, and whatnot.  If the environment you're in sucks, find another.  If the work you do sucks, find something else.  Don't waste your life doing something you hate.  But if you want to pursue working in a team environment, you have to strive to be a better team player. 

Read More
Posted in business, employment, industry, interviews, jobs, people | No comments

Monday, 19 September 2011

What's Wrong with Google+?

Posted on 15:31 by Unknown

I've told this story before, so if you've heard it already, just skip to the next paragraph:  I joined Facebook in October of 2006.  At that time, everyone I know was on MySpace.  The only people on Facebook were college kids (I didn't know at all), and geeks/nerds/dorks drawn by curiosity (whom I also didn't know).  Every friend, colleague, relative and neighbor I asked to join said one of two things:

"I use MySpace.  Why would I switch to Facebook?"

or

"What's Facebook?"

I stuck with it until late 2007 when I grew tired of visiting a social vacuum, closing my account around Christmas of that year.  Then, sometime in 2008, Facebook rolled out a bunch of changes to incorporate new friend features, update streams and, most importantly: games.  Facebook's games seemed to have become the porch light to the mosquitoes of human culture.  All of a sudden, everyone I knew was joining up and the urgency was propelled by an exponential factor.  All I heard in the Fall of 2008 (from those same people) was "You HAVE to join Facebook!  It's the coolest thing!!!"  Talk about drinking the Kool Aid.

social-network

So, I joined back up and played along for a few years.  I then watched as it devolved from an open discussion medium, into a circus festival of game invites, quote repostings, news repeats, religious and political article repostings, stupid animated GIFs postings and more game invites.  The portion of actual discussion fell from somewhere in the 90 percentile of content to less than 10 percent.  Sad.  The tool that was supposed to embolden our "social" interaction became a farce of social distraction.  Sound bitter?  Maybe.  More sad than bitter. 

The momentum seemed to peak in 2010 but I saw a curious erosion of openness following a barrage of political disagreements during and following election time.  The economic aspects that drove a wedge into the heart of our once congenial social climate, played out in emotional arguments over visceral views of "conservative" versus "liberal" and so on.  A lot of people clammed up.  As a safe refuge: rather than cutting each other off abruptly, they hid behind more game scores, game invites, cute video clips of kittens doing stupid tricks, and more reposts of quotes and religious phrases.  Direct communication took a major hit, in general, as compared to only a year or two prior.

So along comes Google+ and again, the cycle repeats:  Nerds are the first to jump on and explore what the hype is all about.  Google tried to make it "hep" by making it invitation-only.  That was cool for about two weeks.  Then the promise of a new model for organizing your social interaction groups with logical channels of thought.  The monolithic model Facebook had relied on for years was now looking outdated.  Then Google shot from the hip at things like privacy settings, export options, and promises for much more cool stuff coming "soon".

"Soon" didn't happen soon enough.  In fact, most of what Google+ users have been waiting for now seems to have been forgotten.  The numbers tell a bleak story: 41% drop in unique posts in the last month alone.  There have been numerous articles and blog posts already on what's wrong with the project and what it should be doing to make things right:

  • Open it up to the public (no more invitations required)
  • Relax the anonymity naming rules
  • Add vanity names for businesses and organizations
  • Integrate other Google services into the fold
  • Improve the mobile app features
  • Add threading to feedback comments
  • Add "Send To" option for Google+ on Google Reader
  • Offer some incentives for Facebook users to spend more time on Google+

The list goes on and on.  But none of these things seem to be happening.  The last six announced feature improvements were trivial adjustments to existing features, rather than radically new capabilities.  Bad move. It feels like a track race where the gun went off, the runner led past the first two hurdles and then, for unknown reasons, decided to walk.

Unless they have some incredibly fantastic amazing mindblowing new feature or incentive coming out soon, I can't see Google reclaiming the excitement and urgency they had during those first two weeks it was brought to life.  The window of opportunity is closing fast.  What a shame too.  I really felt it had something interesting and unique to offer, but this is looking more and more like Google Wave 2.0 now (I mean that in every possible way).  I'll stick with it to the end.  The sad, quiet, dying end... keeping hope alive.

Read More
Posted in facebook, google, people, social stuff, society, web development, web sites | No comments

Saturday, 17 September 2011

A Pictorial Timeline

Posted on 22:11 by Unknown
Let's see if this causes readers to puke their lunches.  If you lose yours, I apologize.  I thought this might be entertaining.  It's me from birth (almost), to today, roughly 47 years.  Like a fine wine (Boone's Farm).

Read More
Posted in people, photos | No comments

Windows 8 Dev Prev - VMware Player Error

Posted on 20:57 by Unknown
This is a bit interesting.  Apparently something changed with respect to how applications query for available memory on the physical host.  At least, as far as how VMware products query for it.  I created a rather mundane Windows 7 32-bit guest machine and tried to launch it, but it won't launch.  Even though I have 8 GB of physical memory on the host, assigning 1 GB to the guest blows its mind.

Read More
Posted in events, virtualization, vmware, windows8 | No comments

Organic Architecture. Part 1

Posted on 11:21 by Unknown
Organic - "4a. Forming an integral element of a whole" / "4b. Having systematic coordination of part" - Merriam Webster Dictionary

Most of you may assume I'm referring to the works of people like Frank Lloyd Wright, or some artist or sculptor.  Close, but no cigar, at least not yet.

I'm going to try to dive into a rather nebulous and obscure topic within the microcosm of software/systems architecture: a term one of my professors once used: "organic architecture".  He didn't articulate this in class, but he did so during a private discussion, and I've always held it in the back of my head when concocting any "solution" to a systematic challenge.  Basically, it denotes the pursuit of designing and building something that just feels "natural".

Trying to quantify that definition would be about as simple as quantifying what makes you feel love or sadness (or what my wife wants for dinner).  But I'm going to try to smoke out some constraints by example to help develop a shape to this concept.  It's going to require multiple parts in order to properly dissect this invisible beast, so hopefully you can (and will want to) bare with me on this journey into nerdville.

Organic Architecture plays a major part in many aspects of our lives and our environment.  From things we participate in, to the tools we use, and the machines we operate and travel within.  It's an inherent part of bio-medicine and chemical engineering, as well as traffic management systems and air traffic control.  It's everywhere.  Rather than try to tie a rope around something this broad in scale, I'm going to break off the tiny chunk that pertains to computer software architecture.

Why?

I really don't know.  It's raining.  My wife is on travel and the house is quiet.  I've been cleaning, cooking, eating, and hanging out with my kids, the cat and dog.  It's one of those brain-incubator environments where the mind wanders and tends to develop ideas that beg to be externalized.  Whoa! I think I just said something logical?  Maybe not.  In any case, this is one small area of software technology that doesn't get much discussion or illumination, anywhere; Not in schools, or conferences or in the workplace.  There are a few books that discuss this but most are obscure and way outside the mainstream for even the geekiest of geeks.  Typically, it is hinted at, rather than outright bagged and tagged.  Some examples I may touch on:
  • Interface Design
  • Systems Management Architecture
  • Configuration Management Architecture
  • Systems State Management
  • Workflow Design
  • Self-Healing Processes

Example 1 - Agent vs Agentless

You've probably heard this term before.  It's used by quite a few products and technologies.  It refers to a basic concept of where nodal processing is performed within a distributed system.  But this concept is not confined to software or technology at all.  It's used in the intelligence community, as it pertains to HUMINT versus SIGINT (geeks, you may commence to beating off over the acronyms... now!).

An "agent" in this context would refer to a component or process which runs on a remote node within a distributed system.  The agent performs the majority of processing locally. In most scenarios, the agent receives general "instructions" or control parameters from a higher "authority" or higher node in the system.  It also typically transmits the results of its processing to a higher authority or node in the system.  A biological example of this would be nerve receptors within the nervous system in the human body.  A computer example would be monitoring agents deployed as part of a systems management technology (e.g. Microsoft System Center Operations Manager®).

An "agentless" scenario would be one where nodes are not configured with any distinct autonomous processing components, but instead are acted upon directly from external/remote nodes in the system.  A social reference example of this would be cash registers in most modern shopping centers (when the power goes out, they cannot function on their own).  A computer example would be a web application, or remote systems data interrogation (think file systems, CIM (WMI), registry, event logs, etc.).

A "system", according to Merriam Webster's Dictionary, can be many things, but in simplest terms: it is a collective body of elements or components that participate in some common goal or outcome.  A football team is a system.  A McDonalds hamburger is a system.  A government is a system.  A farm is a system.

A "distributed system" is not clearly defined by any official dictionary (at least, none that I've encountered), but it basically builds atop the "system" concept to include a qualification of having elements or components which are not physically collocated or in close "proximity".

Putting all of these things together you get one of two distinct concepts for monitoring and managing a distributed collection of components:
  • Agent - components are deployed to each member of the system to perform most of the querying and maintenance of the node locally.
  • Agentless - members of the system are managed directly from a central node (or hierarchical layer node).
This general concept is used for all sorts of functions within a computer system (i.e. network environment).  It's used by software licensing services (e.g. Flexera FlexLM® and FlexNet®), distributed processing (i.e. 3DS Max® "net rendering"), and so on.

Summary

Why is it important or even worthy of knowing about this stuff?  Because the more you see the basic concepts laid out, the more familiar you will be to the "50,000 foot view".  The 50,000 foot view is important because it provides the most general, basic understanding of how something works.  It's how you explain something to someone else who has absolutely no insight or understanding about anything remotely related to the thing you are explaining.  It's also how you keep things in context when a slick vendor rep is pumping your hand and waiting for your signature on the P.O. after he tries to bullshit you into believing they have inventing something "radically new".

In most cases, the "radical" stuff has been around since the 1950's and 1960's (the last era when people actually used their brains to invent new things).  Ever since, most of everything labeled "new" is really a refinement or repackaging of something old.  Knowing what snake oil is, helps you spot new snake oil.

Next Part - Nodal and Agent Autonomy
Read More
Posted in bongloads, programming, psychology, software development, systems architecture, technology, thoughts | No comments

Wednesday, 14 September 2011

Windows 8 - My First 4 Hours

Posted on 19:27 by Unknown
Yep. I'm a sucker for masochistic activities, like beta testing.  It used to pay off, but with most vendors the perks of sticking your neck out and expending time and frustration are not rewarded like they used to be.  I have to suspend my jury decision on Microsoft for now though.

I downloaded Windows 8 Developer Preview 64-bit and ran it inside VMware Workstation 8.0 for a few days before I felt excited enough to unleash it on my Dell Zino 400 HD.  It has an Athlon X2 dual core 1.5 GHz processor with 8 Gb RAM.  It runs Windows 7 Ultimate 64-bit SP1.  I decided to install a bunch of applications, test them on the current platform, then install Windows 8 Dev Preview via an in-place upgrade, and then see how everything works.

General

All of the existing applications are moved under C:\Windows.old\Program Files or C:\Windows.old\Program Files (x86).  Their corresponding shortcuts (on the Task Bar) are updated to change the "Target" path to suit, but the icon paths are not updated on any of them.

Applications

Office 2010 - Does not work. I found each application under the new path (see above) and tried to launch them via their base .exe files (e.g. "WINWORD.exe") but none of them work anymore.  The error is shown below:
Paint.NET 3.5.8 - Does not work.  When I try to launch the .exe file it says that VC++ 2005 SP1 needs to be repaired.  It provides a small dialog form with a "Repair" button, but it does nothing at all.

iTunes 10 - Does not work.  The error is shown below:

TextPad 5.04 - Works.  But, all licensing and customization information is lost and must be re-entered.

TweetDeck - Does not work.  It says I need to install Adobe AIR

IE 10 - Sort of works.  My first trip to YouTube said I needed to install Flash 10, so I did.  Then it works fine.  However, you can launch IE 10 in one of two modes: "immersive" (full-screen, from the tile menu), or "framed" (traditional windowed format).  These two modes are independent and isolated from each other.  You cannot view tabs in one mode from the other, nor can you toggle over to them.  Very odd.

FileZilla 3.5.1 - Works.  But licensing and custom connection settings are lost.

Google Earth 6 - Works.  Opens and begins to render the globe and stars and then says it must close due to an error and aborts. After this, it launches and works fine.  Not sure how consistent this behavior actually will be.

Windows Live Writer 2011 - Does not work.  It says it needs to download, install and enable .NET Framework 3.5.1 and it tries to do that.  It fails.

Google Chrome 15 (dev) - Gone.  Not a trace of it anywhere that I can find it.

Camtasia Studio 7 - Works.  But the first launch will say that required DLL files are not registered.  It prompts to re-register them with elevated privileges (UAC) and succeeded, but then it warns of missing media associations, but then it seems to launch fine.  All licensing information is lost and must be re-entered.


More:

Windows Server Update Services (WSUS) 3.0 Sp2 Admin Console snap-in will not load into MMC.  It says that it is no longer registered.  Attempts to reinstall it have been unsuccessful.  Error is shown below:

The old days of being able to click the "Start" button and start typing something to auto-search for it are gone.  The new "Search" feature requires clicking on "Apps" in order to find things, for example "Snipping Tool", which I use a lot.

Conclusion

If you have a lot of applications you need to ensure reliability going forward, especially if:

A. They are from small vendors that are unlikely to release an update or new version to work on Windows 8.

or

B. They are from big vendors, and you are sure they will release a new version that will cost a shitload of money to handle all of your licenses.

...then you should start testing now.  And I mean NOW, as in RIGHT NOW.  I'm sure things will be fixed and cleaned up, so many of these issues I've encountered may not be a big deal in the end.  I'm also aware that most of you won't do in-place upgrades and that the results of installing things "clean" and "fresh" on a new Windows 8 installation will likely behave much better.  But just in case...
Read More
Posted in applications, software development, testing, thoughts, windows 7, windows8 | No comments
Newer Posts Older Posts Home
Subscribe to: Posts (Atom)

Popular Posts

  • Voting Time: Help Me Out?
    I need to get a better view of how I should manage this blog if I'm going to keep at it. I'd like to know how you typically discover...
  • A World Without Competition
    Try to imagine what things would be like today had there not been fierce competition in certain key parts of our world.  I’ll give you some ...
  • 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 ...
  • Cost
    Software technology, like any technology, provides a means to solving problems.  Some big. Some small.  Some that help.  Some that hurt.  An...
  • Windows 7: Default User vs All Users
    A lot of confusion seems to occur with understanding the difference between the "Default User" profile, and the "All Users...
  • Time to Give Props
    With the ever-expanding volume and breadth of information on the Internet today, it's easy to focus on my own thoughts, experiences, ide...
  • Table of Contents (Preliminary)
    Here's the preliminary Table of Contents for my new book "The AutoCAD Network Administrator's Bible - 2013 Edition".  I...
  • The Nicest IT and IT Vendor Folks I Know
    I've ranted many times before how it's unfair to "hate" an entire company, without providing a rationale for it based on s...
  • Windows 8
    Two small, yet irritating things, that I hope Windows 8 addresses with respect to Windows 7: Being able to put the Recycle Bin in the S...
  • Stupid Assumptions
    After years of watching sci-fi TV shows, movies, etc. it's finally come to a point where even the so-called brightest of our authors and...

Categories

  • a
  • activation
  • active directory
  • advertising
  • agile
  • agility
  • amazon
  • american
  • apple
  • application virtualization
  • applications
  • art
  • articles
  • asp
  • augi
  • authors
  • autocad
  • AutoCAD Autodesk
  • autodesk
  • autolisp
  • automation
  • automotive
  • backups
  • batch
  • beer
  • beta
  • blackberry
  • blogs
  • bongloads
  • book
  • books
  • Books writing kindle amazon technology business projects
  • browsers
  • business
  • cad
  • career
  • certification
  • chrome
  • city government
  • civilization
  • cloud services
  • cmd
  • cmmi
  • comedy
  • command
  • community
  • computers
  • conferences
  • config manager
  • consultants
  • consulting
  • contracting
  • cranium drainium
  • crapware
  • culture
  • data center
  • data mining
  • databases
  • deployment
  • directx
  • DLL
  • domains
  • dumb
  • earth
  • economy
  • editor
  • education
  • election
  • elections
  • employment
  • engineering
  • entertainment
  • environment
  • error monitoring
  • events
  • exchange
  • facebook
  • family
  • firefox
  • flexnet
  • fud
  • fun
  • funny
  • games
  • gary vaynerchuk
  • gmail
  • google
  • government
  • group policy
  • hampton roads
  • health
  • history
  • holidays
  • home
  • html5
  • humor
  • hyper-v
  • iis
  • industry
  • infrastructure
  • installation
  • installshield
  • internet
  • internet explorer
  • interviews
  • jobs
  • jtbworld
  • kindle
  • kixtart
  • lab setup
  • languages
  • ldap
  • learning
  • legal
  • licensing
  • life
  • lifecycle
  • linux
  • lisp
  • logging
  • management
  • manufacturing
  • marketing
  • markets
  • mdop
  • mdt
  • medical
  • messaging
  • microsoft
  • microsoft access
  • military
  • mountains
  • movies
  • mozilla
  • music
  • nature
  • network administration
  • news
  • nook
  • nothing
  • office
  • open source
  • openoffice
  • opera
  • operating systems
  • oracle
  • osx
  • packaging
  • patches
  • people
  • photos
  • podcasts
  • policy
  • politics
  • powershell
  • predictions
  • process automation
  • products
  • programming
  • projects
  • psychology
  • publishing
  • rail
  • reading
  • registry
  • religion
  • reporting
  • reviews
  • rsat
  • rss
  • safari
  • safety
  • sales
  • satire
  • sccm
  • scheduling
  • science
  • scripting
  • search
  • security
  • servers
  • services
  • sharepoint
  • shopping
  • sms
  • social stuff
  • society
  • softgrid
  • software assurance
  • software deployment
  • software development
  • software packaging
  • sony
  • speaking
  • sports
  • sql express
  • sql server
  • statistics
  • Statistics news marketing
  • steve jobs
  • stories
  • stuff
  • stupidity
  • symantec
  • sysinternals
  • system center
  • systems architecture
  • t-sql
  • taxes
  • technet
  • technical support
  • technology
  • TED
  • ted talks
  • testing
  • textpad
  • thoughts
  • traffic
  • training
  • transportation
  • travel
  • troubleshooting
  • tutorials
  • twitter
  • ubuntu
  • unattend
  • unemployment
  • updates
  • upfront ezine
  • utilities
  • vacation
  • vba
  • vbscript
  • video
  • virginia
  • virginia beach
  • virtualization
  • visual lisp
  • vmware
  • vmware server
  • voting
  • war
  • weather
  • web
  • web browsers
  • web development
  • web sites
  • windows
  • windows 7
  • windows live
  • windows server
  • windows server 2012
  • windows8
  • winpe
  • wise
  • wmi
  • work
  • writing
  • ws08
  • wsus
  • wwa
  • x64
  • xml
  • ze frank

Blog Archive

  • ►  2013 (37)
    • ►  October (1)
    • ►  September (5)
    • ►  August (8)
    • ►  July (2)
    • ►  June (4)
    • ►  May (4)
    • ►  April (2)
    • ►  March (2)
    • ►  February (8)
    • ►  January (1)
  • ►  2012 (120)
    • ►  December (14)
    • ►  November (12)
    • ►  October (10)
    • ►  September (7)
    • ►  August (3)
    • ►  July (2)
    • ►  June (6)
    • ►  May (6)
    • ►  April (20)
    • ►  March (16)
    • ►  February (18)
    • ►  January (6)
  • ▼  2011 (343)
    • ►  December (15)
    • ►  November (23)
    • ►  October (27)
    • ▼  September (35)
      • Swallowing Without Looking
      • The Zen of Systems Automation
      • Interaction is Highly Overrated
      • Testing. Testing. Testicles?
      • Autodesk Network Deployment Strategies
      • Slow Autodesk Network Deployments?
      • Querying Services on Remote Computers
      • Test ADO Connection using VBscript
      • 10 Ways to Manage Windows Services
      • 5 Ways to Read Windows Event Logs
      • Automation Gyration
      • 11 Ways to Manipulate the Windows Registry
      • Acad 2012 DirectX - The Final Chapter
      • 10 Easy Ways to Screw Up a Good Computer
      • College Degree vs. Cert vs. Experience
      • Self-Review Time
      • A Friday Mini Braindump
      • What Makes a Great IT Professional
      • What's Wrong with Google+?
      • A Pictorial Timeline
      • Windows 8 Dev Prev - VMware Player Error
      • Organic Architecture. Part 1
      • Windows 8 - My First 4 Hours
      • Windows 7 System Restore: A Lifesaver
      • Moochers Everywhere
      • Changes
      • By The Numbers
      • When You're Bored
      • The Candidates
      • Two Questions
      • Tune In. Turn On. RSS Feed Out
      • Nanny State?
      • Awesometarded?
      • Patching Civil 3D 2011 - Part 3, The Final Chapter
      • Patching Civil 3D 2011 - Part 2
    • ►  August (29)
    • ►  July (17)
    • ►  June (23)
    • ►  May (20)
    • ►  April (38)
    • ►  March (61)
    • ►  February (54)
    • ►  January (1)
Powered by Blogger.

About Me

Unknown
View my complete profile