Wednesday, October 17, 2007
more thoughts on the will to power
another email, this one about power and who has it. why we're all so apathetic and complacent... and overworked and unable or unwilling to try and see what's really going on. without further ado, here comes the sun:
-------------------------------
I really don’t know. Perhaps if we all become more educated, concerned, and, most importantly, involved? But we’ve got other responsibilities. Imagine if wealth were distributed more equitably across the spectrum; if we all went home with a greater percentage in our pockets while CEO’s and Board Members of various companies got less. Imagine if the working poor continued to work, but was not just able to subsist.. if our minimum wage was enough to, if both parents worked, pay the bills and for child care? Imagine that we didn’t have to work two jobs to be able to afford a house and “The American Dream”. Now, imagine… would any of us voluntarily give up that extra time to participate in government?
Judging from the number of people that I’ve heard complain about jury duty, how ineffective voting is, and never attend local town/city hall meetings, I’m guessing few or none. How do we motivate our citizens to get involved? We certainly can’t be compelled by law… we do have state-run educational institutions… and yet, they teach kids to be compliant, unimaginative, to take sides unfairly and arbitrarily based upon silly divisions such as geography or chronological age, and not to be creative, concerned, involved, or educated in the operation, protection, and upholding of our Constitution, both state and federal.
Who has the power? Who wants to keep the power? Who should have the power? Who wants the power? Who has the means to acquire the power? Who has the power to take the power?
Like in Fahrenheit 451, people want their choices to be simple. Fewer choices makes it easy, especially if they can be made without thinking – vote for the side you always vote for or for the one that has the best hair… eventually, people won’t want any choice at all, they just want to go back to having fun and not worrying.
Toward the end of the Roman Empire, citizens worked one-two days to pay their taxes… while armies of slaves took care of all the work. In my opinion, consider the CEO’s and corporate higher ups to be the only real citizens of the US, since they are the only ones who can really exercise a vote with their almighty dollar. Us? well, we’re just the slaves that have to keep the gears greased and turning. Thank goodness we have other slaves to make our food, mow our lawns, change our oil, take care of our children, and wipe our asses when we get too old to do it ourselves.
In the words of Rage Against the Machine, “We gotta take the power back.” and “What better place than here? What better time than now?”
-------------------------------
I really don’t know. Perhaps if we all become more educated, concerned, and, most importantly, involved? But we’ve got other responsibilities. Imagine if wealth were distributed more equitably across the spectrum; if we all went home with a greater percentage in our pockets while CEO’s and Board Members of various companies got less. Imagine if the working poor continued to work, but was not just able to subsist.. if our minimum wage was enough to, if both parents worked, pay the bills and for child care? Imagine that we didn’t have to work two jobs to be able to afford a house and “The American Dream”. Now, imagine… would any of us voluntarily give up that extra time to participate in government?
Judging from the number of people that I’ve heard complain about jury duty, how ineffective voting is, and never attend local town/city hall meetings, I’m guessing few or none. How do we motivate our citizens to get involved? We certainly can’t be compelled by law… we do have state-run educational institutions… and yet, they teach kids to be compliant, unimaginative, to take sides unfairly and arbitrarily based upon silly divisions such as geography or chronological age, and not to be creative, concerned, involved, or educated in the operation, protection, and upholding of our Constitution, both state and federal.
Who has the power? Who wants to keep the power? Who should have the power? Who wants the power? Who has the means to acquire the power? Who has the power to take the power?
Like in Fahrenheit 451, people want their choices to be simple. Fewer choices makes it easy, especially if they can be made without thinking – vote for the side you always vote for or for the one that has the best hair… eventually, people won’t want any choice at all, they just want to go back to having fun and not worrying.
Toward the end of the Roman Empire, citizens worked one-two days to pay their taxes… while armies of slaves took care of all the work. In my opinion, consider the CEO’s and corporate higher ups to be the only real citizens of the US, since they are the only ones who can really exercise a vote with their almighty dollar. Us? well, we’re just the slaves that have to keep the gears greased and turning. Thank goodness we have other slaves to make our food, mow our lawns, change our oil, take care of our children, and wipe our asses when we get too old to do it ourselves.
In the words of Rage Against the Machine, “We gotta take the power back.” and “What better place than here? What better time than now?”
Was Heidegger a bastard?
This is an email that I sent Eric the other day. Probably get my house firebombed by Rush Limbaugh... Nah, it's pretty innocuous.
I'll just cut and paste and do no editing. Eric's email had been something to the effect of well if you had been around when the Nazi's were in power, you'd have gone along with them (it wasn't a slam, just an observation). We were talking about Heidegger after I mentioned trying to learn Spanish and Eric said he could read a little German and Latin... at any rate, I'm becoming long-winded:
--------------------------------------
I would’ve been a Nazi at the time. Much the same way as most of us stand idly by and keep our heads down while the “Patriot Act” is still on the books, and journalists are strong-armed into revealing their sources in the name of “Counter Terrorism”. SO, much the same as the German citizens who claimed, after the war, “we just did what we were told, we had no idea it was that bad”, we go on thinking that Arabs in general are not to be trusted and that the USA is AOK while our CEO (I won’t give him the title of President, he doesn’t deserve it and longer) goes on the books and down in history as officially condoning torture of prisoners. Meanwhile, we are left to consider the things that affect us more day to day, like our jobs and friends and local IT policies.
So, no, I’m not blaming Marty. If I were in his position and Unkle Adolf walks in and says, “Hey, you’re smart, we want you to be our official smart person spokesperson,” even if you think the guy is insane (especially if you think he’s insane actually), there’s no way you’ll turn him down. You’ll thank him for the honor and go about your business, just trying to keep on keeping on, all the while watching your back and hoping it doesn’t get any worse.
Then history makes you into a bastard.
On the other hand, Mr. Sartre can sit in his smoky underground resistance lair and pen all kinds of goodies about responsibility and taking it. Since he’s on the side that can get killed for saying boo… why not go the distance and really lay it on thick? So, Sartre (who was actually involved in the resistance, I’m not calling him a weak-kneed academic) goes down in history as a hero who stood up for his cause and Heidegger goes down in history as Nazi scum. Ironically enough, they’re both Existentialists whose works I greatly admire.
Much like Americans during the time of McCarthyism, and Germans during the Third Reich, think that we’ll look back one day and shake our heads in shame that we let it go that far. Much like Senator Joe finding commies, I think most Americans think Crazy W will just give up if he finds one more terrorist… if he shreds one more amendment to the Constitution.
So, actually, I said it also for humor, but I also chide myself for not being more like Sartre than Heidegger. However, we’re more in the boat of the Germans than the French (insert your own joke there), so we don’t have the “luxury” of being able to put our finger solidly upon something for which we stand, since there’s no oppressor’s boot in our face, rather a velvet glove around our throat.
I'll just cut and paste and do no editing. Eric's email had been something to the effect of well if you had been around when the Nazi's were in power, you'd have gone along with them (it wasn't a slam, just an observation). We were talking about Heidegger after I mentioned trying to learn Spanish and Eric said he could read a little German and Latin... at any rate, I'm becoming long-winded:
--------------------------------------
I would’ve been a Nazi at the time. Much the same way as most of us stand idly by and keep our heads down while the “Patriot Act” is still on the books, and journalists are strong-armed into revealing their sources in the name of “Counter Terrorism”. SO, much the same as the German citizens who claimed, after the war, “we just did what we were told, we had no idea it was that bad”, we go on thinking that Arabs in general are not to be trusted and that the USA is AOK while our CEO (I won’t give him the title of President, he doesn’t deserve it and longer) goes on the books and down in history as officially condoning torture of prisoners. Meanwhile, we are left to consider the things that affect us more day to day, like our jobs and friends and local IT policies.
So, no, I’m not blaming Marty. If I were in his position and Unkle Adolf walks in and says, “Hey, you’re smart, we want you to be our official smart person spokesperson,” even if you think the guy is insane (especially if you think he’s insane actually), there’s no way you’ll turn him down. You’ll thank him for the honor and go about your business, just trying to keep on keeping on, all the while watching your back and hoping it doesn’t get any worse.
Then history makes you into a bastard.
On the other hand, Mr. Sartre can sit in his smoky underground resistance lair and pen all kinds of goodies about responsibility and taking it. Since he’s on the side that can get killed for saying boo… why not go the distance and really lay it on thick? So, Sartre (who was actually involved in the resistance, I’m not calling him a weak-kneed academic) goes down in history as a hero who stood up for his cause and Heidegger goes down in history as Nazi scum. Ironically enough, they’re both Existentialists whose works I greatly admire.
Much like Americans during the time of McCarthyism, and Germans during the Third Reich, think that we’ll look back one day and shake our heads in shame that we let it go that far. Much like Senator Joe finding commies, I think most Americans think Crazy W will just give up if he finds one more terrorist… if he shreds one more amendment to the Constitution.
So, actually, I said it also for humor, but I also chide myself for not being more like Sartre than Heidegger. However, we’re more in the boat of the Germans than the French (insert your own joke there), so we don’t have the “luxury” of being able to put our finger solidly upon something for which we stand, since there’s no oppressor’s boot in our face, rather a velvet glove around our throat.
Thursday, September 06, 2007
Vista SP1 is coming
I'm sure that anyone who uses Vista will appreciate that SP1 is coming in the second half of 2007. Better domain performance, better coping and extraction of files, better hibernate and resume funtionality... all the stuff that you'd expect from a first service pack. I may actually start deploying it on something other than the laptops at work.
And for those that are using VIsta now, and are irritated becuase you can't find a quick way to access the network settings quiclly in Vista, well I have the answer for you. You used to be able to just right click and go to properties for My Network Places and hey presto... now, you have to right-click, go to Network and SHaring Center and then go to Manage Network Connections, and then finally you get to the network properties. Well, mein freund, it's easy when you know the command. I poked around a bit in the SYSTEM32 directory, looking for CPL files (Control Panel) and EXE's of interest. The old standby's are all there - throwbacks to an older time, like MAIN.CPL which is the mouse properties and DESK.CPL which is the Display Properties... then I started taking note of new CPL applets... and one-by-one I tried them and finally had the answer and the quick way to start it: at any Command or Run Prompt, just put in NCPA.CPL and TADA!!! you have the network connections folder at your fingertips.
NOW THAT'S A HAPPY DEVELOPMENT! W00t!
And for those that are using VIsta now, and are irritated becuase you can't find a quick way to access the network settings quiclly in Vista, well I have the answer for you. You used to be able to just right click and go to properties for My Network Places and hey presto... now, you have to right-click, go to Network and SHaring Center and then go to Manage Network Connections, and then finally you get to the network properties. Well, mein freund, it's easy when you know the command. I poked around a bit in the SYSTEM32 directory, looking for CPL files (Control Panel) and EXE's of interest. The old standby's are all there - throwbacks to an older time, like MAIN.CPL which is the mouse properties and DESK.CPL which is the Display Properties... then I started taking note of new CPL applets... and one-by-one I tried them and finally had the answer and the quick way to start it: at any Command or Run Prompt, just put in NCPA.CPL and TADA!!! you have the network connections folder at your fingertips.
NOW THAT'S A HAPPY DEVELOPMENT! W00t!
Monday, February 05, 2007
arrrrgh!!!
Eric and I had joked around previously about how I don't like pretty much anything Victorian, particulalry the novels, stating that they needed more excitement - you know, ninjas or pirates or something (I'm paraphrasing the conversation to make this all sound like my idea). So Eric mentioned that while watching the show on PBS this weekend, he "kept thinking 'this would be the perfect time for Ninjas to show up- or maybe pirates.'" So I obliged both of our fantasies with this image. I thought that it turned out well.
Apropos of their sneakiness, pictures of ninjas were harder to come by than scantily clad women in pirate outfits. ^_^
Thursday, February 01, 2007
"server transmogrification: how I played the shell game and won," a play in five acts
server transmogrification: how I played the shell game and won a play in five acts
cast of characters:
The Sysop (MSCE Extraordinaire)
The Sysop’s PC (Dell Optiplex 745, Vista Workstation)
The Sysop’s Home PC (Homegrown goodness)
The Sysop’s Wife (Beautiful, classy, and sassy)
The New Server (Dell PowerEdge 2900)
The RAC (Dell Remote Access Controller)
The Old Server (Dell PowerEdge SC1420)
The Switch (Cisco Catalyst 3560G Managed switch)
The Terminal Server (Old Windows2000 DC)
The Backup (external 80GB USB hard drive)
The Old Install CD (Small Business Server media)
The Floppy (Floppy disk with RAID drivers)
The Temporary O/S (Windows XP Volume License and key)
The New Install CD (SBS 2003 R2 Upgrade)
The Transition CD’s (SBS 2003 Transition Pack CD 1 &2)
The New CAL’s (3 SBS 2003 CAL Transition Packs)
The Terminal Server (Old Windows2000 DC)
Prologue:
In fair Viroqua where we lay our scene, a production environment, which utilizes four servers in three locations. The Old Server, an aging king, must be succeeded by his stalwart son – a dual processing, quad core warrior, who will lead the kingdom to ever-greater heights. The succession must happen during off-hours. The Sysop, who desires nothing more than to work his arcane magic from afar, so at to be able to kick back and enjoy the comforts of his abode rather than the fluorescent oppression of the office, must complete the succession in secret so that the citizens of the kingdom never know that the Old King was deposed and the New King has been seated on the throne, for all know that the people are a superstitious lot and if they know that succession is to occur, their panic may cause the kingdom to crumble. Thusly do we begin as the Sysop develops the spells necessary to make the change remotely, legally, and seamlessly…
ACT I – Thursday’s Preparations
Act I, Scene I, The RAC sings:
Thursday Morning, The Sysop’s Office
Enter Stage Right: The New Server, The Old Server, The Switch, The Backup, The Sysop PC
The New Server is setup and tested to be sure that all hardware was working, during which time the BIOS is set to boot first to CD, then to RAID, then to floppy. The RAC is setup to use a static IP. The RAID is configured as RAID5 with a hot spare because The Sysop is never too careful. Console access is obtained from The Sysop PC via browser. The Sysop giggles maniacally, then sets up a dedicated port on The Switch for The Older Server, The New Server, and The RAC.
Act I, Scene II, The Sysop PC creates Images:
Later Thursday, The Sysop’s Office
Enter stage right, The New Install CD and The Transition CD; enter stage left, The Sysop PC and The Backup
The Sysop PC makes ISO images of the The New Install CD and The Transition CD 1&2 and the Dell Drive CD using free ISO recorder software. These images are placed on The Backup, along with free ISO mounting software and text file with keys for upgrades. The ADPREP folder is copied from The Transition CD2 to The Old Server. From the console of The Old Server ADPREP /ForestPrep is run successfully, receiving the following information:
Opened Connection to The Old Server
SSPI Bind succeeded
Current Schema Version is 30
Upgrading schema to version 31
Connecting to "The Old Server"
Logging in as current user using SSPI
Importing directory from file "C:\WINDOWS\system32\sch31.ldf”
Loading entries.............................................
............................................................
139 entries modified successfully.
The command has completed successfully
Adprep successfully updated the forest-wide information…
A little giddy, The Sysop begins to giggle.
Act I, Scene III, The Temporary O/S and The Backup make ready for the assault
Even Later Thursday, The Sysop’s Office
Light come up on an already occupied stage, The New Server and The RAC wait patiently. The Temporary O/S and The Floppy enter whistling.
The New Server is loaded with The Temporary O/S with the help of The Floppy, during which The New Server takes on a temporary name. After the final reboot, the system’s firewall is turned off and The Old Install CD is placed in the drive.
Enter The Backup, Stage Left, The Floppy exits, stage right
The Backup is connected to The New Server. Both lie in wait.
ACT II – Friday’s Backup
Act II, Scene I, The Backup makes good, The Floppy gets updated
Friday, day’s end, The Sysop’s Office
Enter The OId Server, Stage Left
Via Remote Desktop, The Drive Mapping is created on The Older Server, mapping to The Backup on The New Server utilizing the NET USE command and the administrative share name for the backup. The Sysop logs on to the third-party spam service utilized by The Sysop’s company, mumbling about their lousy customer service and how much he hates them overall and how he’s looking forward to dropping their crap services when their contract is up, and sets the system to spool all incoming messages durint the down-time.
The Sysop then runs an ASR backup on The Old Server, using The Floppy as the destination for the ASR files and The Mapped Drive as the Destination. After the backup is begun, The Floppy, now pregnant with RAID and ASR files exits.
Exit The Sysop and The Floppy stage left.
The Sysop verifies the backup is running properly and giggle maniacally again.
Act II, Scene II, The Stage is set for revolution
Later, The Sysop’s Office
As the lights come up The Floppy enter stage right; The New Server, disguised as a workstation sits and waits.
The clickety clack of data backing up The Backup fills the air as The Sysop places The Floppy in The New Server and heads for home.
Exit, The Sysop, Stage right
ACT III – Saturday’s Uprising
Act III, Scene I: Hallowed be thy remote
Saturday Morning, The Sysop’s Home
As the lights come up, The Sysop can be seen logging on to the network viaThe Terminal Server in the Production Environment. He piggybacks over to The Sysop PC via Remote Desktop.
Beer in hand, The Sysop logs on and verifies that the ASR Backup has completed on The Old Server. The Switch is logged onto and the port for The Old Server and The New Server are disabled for the time being. He then uses The RAC on The New Server to reboot the system, being sure to “Press Any Key to Boot to CD,” “Press F6 to load a Third Party RAID Driver,” and “Press F2 to begin ASR process.” With The Floppy in the drive, The New Server gets a healthy dose of RAID Drivers and ASR configuration. When asked for the location of the backup files, The Backup, which has patiently bided its time, springs to the forefront, fat with data. The restore begins in earnest. The Sysop giggles maniacally.
Act III, Scene II: The driver dance
Later Saturday Morning, The Sysop’s Home
Softly humming “The Safety Dance” The Sysop enters stage right and sits at the Sysop’s Home PC.
The restore process has ended and The New Server has rebooted, looking suspiciously like The Old Server. The Sysop mounts the driver CD and installs various and sundry drivers, ignoring the remark that the hardware has changed significantly on the system and that it need to be reactivated. He thinks out loud to no one in particular – “You won’t be running the same O/S long enough to worry about not having the right license, my friend.” Then he laughs manically and goes to get another beer
Exit The Sysop stage right.
Act III, Scene III: Hold all my calls
Later Saturday, The Sysop’s Home
Re-enter The Sysop stage right.
Still working via Terminal Services, The Sysop guzzles his beer and disables The Old Server’s port on The Switch, to make sure that no other systems notice that he is going to secretly replace the server they’ve normally been drinking with a new cup of coffee. But to make sure that all remains legal, he has to deal with the old OEM license. He cracks his fingers and heads out for another beer.
ACT IV – The Old Switcheroo
Act IV, Scene I: Time for your shot
Saturday Afternoon, The Sysop’s Home
Enter The Sysop stage right, yet another beer in hand, hummin, to his surprise, an old Queenrsryche tune. Worried that he is getting too drunk, he starts up some music on The Sysop’s Home PC and returns to the task at hand.
The New Install CD is now mounted on The New Server. Exchange 2003 has Service Pack 2 applied, and SharePoint doesn’t need it because it’s already been applied. SBS Server gets updated to R2 and is rebooted. Nervous that he may be sobering up The Sysop scurries for a beer.
Act IV, Scene II: Transitional Mogrification
Later Saturday Afternoon, The Sysop’s Home
Enter The Sysop, stage right, holding two beers. He staggers to his seat and mumbles.
“Where’s my checklist? Oh yeah yeah yeah, I got it. Transition Pack. HAH!”
The Sysop mounts The Transition Pack CD 1 and enters the key from the text file on The Backup. He starts the setup process, specifies the key and enters the admin password so that the system can reboot of its own accord. He sits and waits, clicking OK every here and there when warned that services or drivers did not load, mumbles, belches, and surfs “educational” sites on the Internet while waiting.
The Sysop falls asleep as the lights go down.
Act IV, Scene III: Transitional Dreams
Late Saturday Afternoon, The Sysop’s Home
The lights come up dimly and fog floods the stage, The Sysop sits at The Sysop’s Home PC, clicking mechanically, eyes closed. He mutters and grunts.
Above his head, visions of failed upgrades and arcane errors dance. Red glowing X’s. Angry flashing FAILED Signs. The Sysop slumbers on while the upgrade continues. At one point he raises his head and clicks OK when the server worries about bad things happening. The dream ends and The Sysop rises to go to the bathroom.
Exit The Sysop stage right.
Act IV, Scene IV: Transitional Realities
Early Saturday Evening, The Sysop’s Home
Enter The Sysop stage right, espresso in hand. Reseated and now very serious he begins the process that affects other servers in the enterprise.
The Sysop now enables the port for The New Server, now running Server 2003 Service Pack 1, on The Switch. He minimizes his RDP connection and runs REPLMON from The Terminal Server and forces Active Directory Replication between The Terminal Server and The New Server. Satisfied when it completes, he closes his Terminal Services session and vows to complete the task tomorrow.
ACT V РD̩nouement
Act V, Scene I: Satisfaction
Saturday Evening, Out on the Town
The lights come up and The Sysop can be seen having dinner with his The Sysop’s Wife , flushed with success. Soft music plays and the scene fades.
Act V, Scene II: Activate the sleeper cell
Sunday Morning, The Sysop’s House
Enter The Sysop stage right, drinking espresso and casually rubbing his head, smiling. He logs on to The Terminal Server and picks up where he left off.
Windows is successfully activated, since the system is now running a valid FPP license. The Transition CD 2 is mounted and setup continues. After warnings that his head may explode or his dog may die if the upgrade goes awry, Server2003 R2 setup is run and completed successfully. The Sysop peers at the clock wondering if it is too early to have a beer.
Exit The Sysop stage right
Act V, Scene III: Testing the services
Later Sunday Morning, The Sysop’s House
Enter The Sysop stage right, drinking a water, since it’s still pretty early.
After The Upgrade Process is complete, the spam filtering agency is contacted and the system is taken of Spooling. Test emails are sent to verify connectivity. The Sysop connects to several PC’s in the domain and logs on as an end-user to verify that Group Policy is applying and things like Folder Redirection and drive mappings are occurring. Satisfied that all is operational and working fine, The Sysop pats himself on the back and rechecks the time, which is now 12:01PM. Grinning he rises and walks out.
Exit The Sysop stage right. Moments pass and he returns, with A Beer.
Smiling to himself, The Sysop drinks his beer and logs off all of his sessions. He raises his can and whispers. “The King is dead, long live the King.” He smiles knowing that The Old Server will have new adventures in the weeks to come, being deployed as a minor Duke in a Branch Office, but that, is another story…
Curtain call.
FIN
cast of characters:
The Sysop (MSCE Extraordinaire)
The Sysop’s PC (Dell Optiplex 745, Vista Workstation)
The Sysop’s Home PC (Homegrown goodness)
The Sysop’s Wife (Beautiful, classy, and sassy)
The New Server (Dell PowerEdge 2900)
The RAC (Dell Remote Access Controller)
The Old Server (Dell PowerEdge SC1420)
The Switch (Cisco Catalyst 3560G Managed switch)
The Terminal Server (Old Windows2000 DC)
The Backup (external 80GB USB hard drive)
The Old Install CD (Small Business Server media)
The Floppy (Floppy disk with RAID drivers)
The Temporary O/S (Windows XP Volume License and key)
The New Install CD (SBS 2003 R2 Upgrade)
The Transition CD’s (SBS 2003 Transition Pack CD 1 &2)
The New CAL’s (3 SBS 2003 CAL Transition Packs)
The Terminal Server (Old Windows2000 DC)
Prologue:
In fair Viroqua where we lay our scene, a production environment, which utilizes four servers in three locations. The Old Server, an aging king, must be succeeded by his stalwart son – a dual processing, quad core warrior, who will lead the kingdom to ever-greater heights. The succession must happen during off-hours. The Sysop, who desires nothing more than to work his arcane magic from afar, so at to be able to kick back and enjoy the comforts of his abode rather than the fluorescent oppression of the office, must complete the succession in secret so that the citizens of the kingdom never know that the Old King was deposed and the New King has been seated on the throne, for all know that the people are a superstitious lot and if they know that succession is to occur, their panic may cause the kingdom to crumble. Thusly do we begin as the Sysop develops the spells necessary to make the change remotely, legally, and seamlessly…
ACT I – Thursday’s Preparations
Act I, Scene I, The RAC sings:
Thursday Morning, The Sysop’s Office
Enter Stage Right: The New Server, The Old Server, The Switch, The Backup, The Sysop PC
The New Server is setup and tested to be sure that all hardware was working, during which time the BIOS is set to boot first to CD, then to RAID, then to floppy. The RAC is setup to use a static IP. The RAID is configured as RAID5 with a hot spare because The Sysop is never too careful. Console access is obtained from The Sysop PC via browser. The Sysop giggles maniacally, then sets up a dedicated port on The Switch for The Older Server, The New Server, and The RAC.
Act I, Scene II, The Sysop PC creates Images:
Later Thursday, The Sysop’s Office
Enter stage right, The New Install CD and The Transition CD; enter stage left, The Sysop PC and The Backup
The Sysop PC makes ISO images of the The New Install CD and The Transition CD 1&2 and the Dell Drive CD using free ISO recorder software. These images are placed on The Backup, along with free ISO mounting software and text file with keys for upgrades. The ADPREP folder is copied from The Transition CD2 to The Old Server. From the console of The Old Server ADPREP /ForestPrep is run successfully, receiving the following information:
Opened Connection to The Old Server
SSPI Bind succeeded
Current Schema Version is 30
Upgrading schema to version 31
Connecting to "The Old Server"
Logging in as current user using SSPI
Importing directory from file "C:\WINDOWS\system32\sch31.ldf”
Loading entries.............................................
............................................................
139 entries modified successfully.
The command has completed successfully
Adprep successfully updated the forest-wide information…
A little giddy, The Sysop begins to giggle.
Act I, Scene III, The Temporary O/S and The Backup make ready for the assault
Even Later Thursday, The Sysop’s Office
Light come up on an already occupied stage, The New Server and The RAC wait patiently. The Temporary O/S and The Floppy enter whistling.
The New Server is loaded with The Temporary O/S with the help of The Floppy, during which The New Server takes on a temporary name. After the final reboot, the system’s firewall is turned off and The Old Install CD is placed in the drive.
Enter The Backup, Stage Left, The Floppy exits, stage right
The Backup is connected to The New Server. Both lie in wait.
ACT II – Friday’s Backup
Act II, Scene I, The Backup makes good, The Floppy gets updated
Friday, day’s end, The Sysop’s Office
Enter The OId Server, Stage Left
Via Remote Desktop, The Drive Mapping is created on The Older Server, mapping to The Backup on The New Server utilizing the NET USE command and the administrative share name for the backup. The Sysop logs on to the third-party spam service utilized by The Sysop’s company, mumbling about their lousy customer service and how much he hates them overall and how he’s looking forward to dropping their crap services when their contract is up, and sets the system to spool all incoming messages durint the down-time.
The Sysop then runs an ASR backup on The Old Server, using The Floppy as the destination for the ASR files and The Mapped Drive as the Destination. After the backup is begun, The Floppy, now pregnant with RAID and ASR files exits.
Exit The Sysop and The Floppy stage left.
The Sysop verifies the backup is running properly and giggle maniacally again.
Act II, Scene II, The Stage is set for revolution
Later, The Sysop’s Office
As the lights come up The Floppy enter stage right; The New Server, disguised as a workstation sits and waits.
The clickety clack of data backing up The Backup fills the air as The Sysop places The Floppy in The New Server and heads for home.
Exit, The Sysop, Stage right
ACT III – Saturday’s Uprising
Act III, Scene I: Hallowed be thy remote
Saturday Morning, The Sysop’s Home
As the lights come up, The Sysop can be seen logging on to the network viaThe Terminal Server in the Production Environment. He piggybacks over to The Sysop PC via Remote Desktop.
Beer in hand, The Sysop logs on and verifies that the ASR Backup has completed on The Old Server. The Switch is logged onto and the port for The Old Server and The New Server are disabled for the time being. He then uses The RAC on The New Server to reboot the system, being sure to “Press Any Key to Boot to CD,” “Press F6 to load a Third Party RAID Driver,” and “Press F2 to begin ASR process.” With The Floppy in the drive, The New Server gets a healthy dose of RAID Drivers and ASR configuration. When asked for the location of the backup files, The Backup, which has patiently bided its time, springs to the forefront, fat with data. The restore begins in earnest. The Sysop giggles maniacally.
Act III, Scene II: The driver dance
Later Saturday Morning, The Sysop’s Home
Softly humming “The Safety Dance” The Sysop enters stage right and sits at the Sysop’s Home PC.
The restore process has ended and The New Server has rebooted, looking suspiciously like The Old Server. The Sysop mounts the driver CD and installs various and sundry drivers, ignoring the remark that the hardware has changed significantly on the system and that it need to be reactivated. He thinks out loud to no one in particular – “You won’t be running the same O/S long enough to worry about not having the right license, my friend.” Then he laughs manically and goes to get another beer
Exit The Sysop stage right.
Act III, Scene III: Hold all my calls
Later Saturday, The Sysop’s Home
Re-enter The Sysop stage right.
Still working via Terminal Services, The Sysop guzzles his beer and disables The Old Server’s port on The Switch, to make sure that no other systems notice that he is going to secretly replace the server they’ve normally been drinking with a new cup of coffee. But to make sure that all remains legal, he has to deal with the old OEM license. He cracks his fingers and heads out for another beer.
ACT IV – The Old Switcheroo
Act IV, Scene I: Time for your shot
Saturday Afternoon, The Sysop’s Home
Enter The Sysop stage right, yet another beer in hand, hummin, to his surprise, an old Queenrsryche tune. Worried that he is getting too drunk, he starts up some music on The Sysop’s Home PC and returns to the task at hand.
The New Install CD is now mounted on The New Server. Exchange 2003 has Service Pack 2 applied, and SharePoint doesn’t need it because it’s already been applied. SBS Server gets updated to R2 and is rebooted. Nervous that he may be sobering up The Sysop scurries for a beer.
Act IV, Scene II: Transitional Mogrification
Later Saturday Afternoon, The Sysop’s Home
Enter The Sysop, stage right, holding two beers. He staggers to his seat and mumbles.
“Where’s my checklist? Oh yeah yeah yeah, I got it. Transition Pack. HAH!”
The Sysop mounts The Transition Pack CD 1 and enters the key from the text file on The Backup. He starts the setup process, specifies the key and enters the admin password so that the system can reboot of its own accord. He sits and waits, clicking OK every here and there when warned that services or drivers did not load, mumbles, belches, and surfs “educational” sites on the Internet while waiting.
The Sysop falls asleep as the lights go down.
Act IV, Scene III: Transitional Dreams
Late Saturday Afternoon, The Sysop’s Home
The lights come up dimly and fog floods the stage, The Sysop sits at The Sysop’s Home PC, clicking mechanically, eyes closed. He mutters and grunts.
Above his head, visions of failed upgrades and arcane errors dance. Red glowing X’s. Angry flashing FAILED Signs. The Sysop slumbers on while the upgrade continues. At one point he raises his head and clicks OK when the server worries about bad things happening. The dream ends and The Sysop rises to go to the bathroom.
Exit The Sysop stage right.
Act IV, Scene IV: Transitional Realities
Early Saturday Evening, The Sysop’s Home
Enter The Sysop stage right, espresso in hand. Reseated and now very serious he begins the process that affects other servers in the enterprise.
The Sysop now enables the port for The New Server, now running Server 2003 Service Pack 1, on The Switch. He minimizes his RDP connection and runs REPLMON from The Terminal Server and forces Active Directory Replication between The Terminal Server and The New Server. Satisfied when it completes, he closes his Terminal Services session and vows to complete the task tomorrow.
ACT V РD̩nouement
Act V, Scene I: Satisfaction
Saturday Evening, Out on the Town
The lights come up and The Sysop can be seen having dinner with his The Sysop’s Wife , flushed with success. Soft music plays and the scene fades.
Act V, Scene II: Activate the sleeper cell
Sunday Morning, The Sysop’s House
Enter The Sysop stage right, drinking espresso and casually rubbing his head, smiling. He logs on to The Terminal Server and picks up where he left off.
Windows is successfully activated, since the system is now running a valid FPP license. The Transition CD 2 is mounted and setup continues. After warnings that his head may explode or his dog may die if the upgrade goes awry, Server2003 R2 setup is run and completed successfully. The Sysop peers at the clock wondering if it is too early to have a beer.
Exit The Sysop stage right
Act V, Scene III: Testing the services
Later Sunday Morning, The Sysop’s House
Enter The Sysop stage right, drinking a water, since it’s still pretty early.
After The Upgrade Process is complete, the spam filtering agency is contacted and the system is taken of Spooling. Test emails are sent to verify connectivity. The Sysop connects to several PC’s in the domain and logs on as an end-user to verify that Group Policy is applying and things like Folder Redirection and drive mappings are occurring. Satisfied that all is operational and working fine, The Sysop pats himself on the back and rechecks the time, which is now 12:01PM. Grinning he rises and walks out.
Exit The Sysop stage right. Moments pass and he returns, with A Beer.
Smiling to himself, The Sysop drinks his beer and logs off all of his sessions. He raises his can and whispers. “The King is dead, long live the King.” He smiles knowing that The Old Server will have new adventures in the weeks to come, being deployed as a minor Duke in a Branch Office, but that, is another story…
Curtain call.
FIN
"server transmogrification: how I played the shell game and won," a play in five acts
server transmogrification: how I played the shell game and won
a play in five acts
cast of characters:
The Sysop (MSCE Extraordinaire)
The Sysop’s PC (Dell Optiplex 745, Vista Workstation)
The Sysop’s Home PC (Homegrown goodness)
The Sysop’s Wife (Beautiful, classy, and sassy)
The New Server (Dell PowerEdge 2900)
The RAC (Dell Remote Access Controller)
The Old Server (Dell PowerEdge SC1420)
The Switch (Cisco Catalyst 3560G Managed switch)
The Terminal Server (Old Windows2000 DC)
The Backup (external 80GB USB hard drive)
The Old Install CD (Small Business Server media)
The Floppy (Floppy disk with RAID drivers)
The Temporary O/S (Windows XP Volume License and key)
The New Install CD (SBS 2003 R2 Upgrade)
The Transition CD’s (SBS 2003 Transition Pack CD 1 &2)
The New CAL’s (3 SBS 2003 CAL Transition Packs)
The Terminal Server (Old Windows2000 DC)
Prologue:
In fair Viroqua where we lay our scene, a production environment, which utilizes four servers in three locations. The Old Server, an aging king, must be succeeded by his stalwart son – a dual processing, quad core warrior, who will lead the kingdom to ever-greater heights. The succession must happen during off-hours. The Sysop, who desires nothing more than to work his arcane magic from afar, so at to be able to kick back and enjoy the comforts of his abode rather than the fluorescent oppression of the office, must complete the succession in secret so that the citizens of the kingdom never know that the Old King was deposed and the New King has been seated on the throne, for all know that the people are a superstitious lot and if they know that succession is to occur, their panic may cause the kingdom to crumble. Thusly do we begin as the Sysop develops the spells necessary to make the change remotely, legally, and seamlessly…
ACT I – Thursday’s Preparations
Act I, Scene I, The RAC sings:
Thursday Morning, The Sysop’s Office
Enter Stage Right: The New Server, The Old Server, The Switch, The Backup, The Sysop PC
The New Server was setup and tested to be sure that all hardware was working, during which time the BIOS is set to boot first to CD, then to RIAD, then to floppy. The RAC is setup to use a static IP. The RAID is configured as RAID5 with a hot spare because The Sysop is never too careful. Console access is obtained from The Sysop PC via browser. The Sysop giggles maniacally, then sets up a dedicated port on The Switch for The Older Server, The New Server, and The RAC.
Act I, Scene II, The Sysop PC creates Images:
Later Thursday, The Sysop’s Office
Enter stage right, The New Install CD and The Transition CD; enter stage left, The Sysop PC and The Backup
The Sysop PC makes ISO images of the The New Install CD and The Transition CD 1&2 and the Dell Drive CD using free ISO recorder software. These images are placed on The Backup, along with free ISO mounting software and text file with keys for upgrades. The ADPREP folder is copied from The Transition CD2 to The Old Server. From the console of The Old Server ADPREP /ForestPrep is run successfully, receiving the following information:
Opened Connection to The Old Server
SSPI Bind succeeded
Current Schema Version is 30
Upgrading schema to version 31
Connecting to "The Old Server"
Logging in as current user using SSPI
Importing directory from file "C:\WINDOWS\system32\sch31.ldf”
Loading entries.............................................
............................................................
139 entries modified successfully.
The command has completed successfully
Adprep successfully updated the forest-wide information…
A little giddy, The Sysop begins to giggle.
Act I, Scene III, The Temporary O/S and The Backup make ready for the assault
Even Later Thursday, The Sysop’s Office
Light come up on an already occupied stage, The New Server and The RAC wait patiently. The Temporary O/S and The Floppy enter whistling.
The New Server is loaded with The Temporary O/S with the help of The Floppy, during which The New Server takes on a temporary name. After the final reboot, the system’s firewall is turned off and The Old Install CD is placed in the drive.
Enter The Backup, Stage Left, The Floppy exits, stage right
The Backup is connected to The New Server. Both lie in wait.
ACT II – Friday’s Backup
Act II, Scene I, The Backup makes good, The Floppy gets updated
Friday, day’s end, The Sysop’s Office
Enter The OId Server, Stage Left
Via Remote Desktop, The Drive Mapping is created on The Older Server, mapping to The Backup on The New Server utilizing the NET USE command and the administrative share name for the backup. The Sysop logs on to the third-party spam service utilized by The Sysop’s company, mumbling about their lousy customer service and how much he hates them overall and how he’s looking forward to dropping their crap services when their contract is up, and sets the system to spool all incoming messages durint the down-time.
The Sysop then runs an ASR backup on The Old Server, using The Floppy as the destination for the ASR files and The Mapped Drive as the Destination. After the backup is begun, The Floppy, now pregnant with RAID and ASR files exits.
Exit The Sysop and The Floppy stage left.
The Sysop verifies the backup is running properly and giggle maniacally again.
Act II, Scene II, The Stage is set for revolution
Later, The Sysop’s Office
As the lights come up The Floppy enter stage right; The New Server, disguised as a workstation sits and waits.
The clickety clack of data backing up The Backup fills the air as The Sysop places The Floppy in The New Server and heads for home.
Exit, The Sysop, Stage right
ACT III – Saturday’s Uprising
Act III, Scene I: Hallowed be thy remote
Saturday Morning, The Sysop’s Home
As the lights come up, The Sysop can be seen logging on to the network viaThe Terminal Server in the Production Environment. He piggybacks over to The Sysop PC via Remote Desktop.
Beer in hand, The Sysop logs on and verifies that the ASR Backup has completed on The Old Server. The Switch is logged onto and the port for The Old Server and The New Server are disabled for the time being. He then uses The RAC on The New Server to reboot the system, being sure to “Press Any Key to Boot to CD,” “Press F6 to load a Third Party RAID Driver,” and “Press F2 to begin ASR process.” With The Floppy in the drive, The New Server gets a healthy dose of RAID Drivers and ASR configuration. When asked for the location of the backup files, The Backup, which has patiently bided its time, springs to the forefront, fat with data. The restore begins in earnest. The Sysop giggles maniacally.
Act III, Scene II: The driver dance
Later Saturday Morning, The Sysop’s Home
Softly humming “The Safety Dance” The Sysop enters stage right and sits at the Sysop’s Home PC.
The restore process has ended and The New Server has rebooted, looking suspiciously like The Old Server. The Sysop mounts the driver CD and installs various and sundry drivers, ignoring the remark that the hardware has changed significantly on the system and that it need to be reactivated. He thinks out loud to no one in particular – “You won’t be running the same O/S long enough to worry about not having the right license, my friend.” Then he laughs manically and goes to get another beer
Exit The Sysop stage right.
Act III, Scene III: Hold all my calls
Later Saturday, The Sysop’s Home
Re-enter The Sysop stage right.
Still working via Terminal Services, The Sysop guzzles his beer and disables The Old Server’s port on The Switch, to make sure that no other systems notice that he is going to secretly replace the server they’ve normally been drinking with a new cup of coffee. But to make sure that all remains legal, he has to deal with the old OEM license. He cracks his fingers and heads out for another beer.
ACT IV – The Old Switcheroo
Act IV, Scene I: Time for your shot
Saturday Afternoon, The Sysop’s Home
Enter The Sysop stage right, yet another beer in hand, hummin, to his surprise, an old Queenrsryche tune. Worried that he is getting too drunk, he starts up some music on The Sysop’s Home PC and returns to the task at hand, tapping his foot to The Dresden Dolls.
The New Install CD is now mounted on The New Server. Exchange 2003 has Service Pack 2 applied, and SharePoint doesn’t need it because it’s already been applied. SBS Server gets updated to R2 and is rebooted. Nervous that he may be sobering up The Sysop scurries for a beer.
Act IV, Scene II: Transitional Mogrification
Later Saturday Afternoon, The Sysop’s Home
Enter The Sysop, stage right, holding two beers. He staggers to his seat and mumbles.
“Where’s my checklist? Oh yeah yeah yeah, I got it. Transition Pack. HAH!”
The Sysop mounts The Transition Pack CD 1 and enters the key from the text file on The Backup. He starts the setup process, specifies the key and enters the admin password so that the system can reboot of its own accord. He sits and waits, clicking OK every here and there when warned that services or drivers did not load, mumbles, belches, and surfs “educational” sites on the Internet while waiting.
The Sysop falls asleep as the lights go down.
Act IV, Scene III: Transitional Dreams
Late Saturday Afternoon, The Sysop’s Home
The lights come up dimly and fog floods the stage, The Sysop sits at The Sysop’s Home PC, clicking mechanically, eyes closed. He mutters and grunts.
Above his head, visions of failed upgrades and arcane errors dance. Red glowing X’s. Angry flashing FAILED Signs. The Sysop slumbers on while the upgrade continues. At one point he raises his head and clicks OK when the server worries about bad things happening. The dream ends and The Sysop rises to go to the bathroom.
Exit The Sysop stage right.
Act IV, Scene IV: Transitional Realities
Early Saturday Evening, The Sysop’s Home
Enter The Sysop stage right, espresso in hand. Reseated and now very serious he begins the process that affects other servers in the enterprise.
The Sysop now enables the port for The New Server, now running Server 2003 Service Pack 1, on The Switch. He minimizes his RDP connection and runs REPLMON from The Terminal Server and forces Active Directory Replication between The Terminal Server and The New Server. Satisfied when it completes, he closes his Terminal Services session and vows to complete the task tomorrow.
ACT V РD̩nouement
Act V, Scene I: Satisfaction
Saturday Evening, Out on the Town
The lights come up and The Sysop can be seen having dinner with his The Sysop’s Wife , flushed with success. Soft music plays and the scene fades.
Act V, Scene II: Activate the sleeper cell
Sunday Morning, The Sysop’s House
Enter The Sysop stage right, drinking espresso and casually rubbing his head, smiling. He logs on to The Terminal Server and picks up where he left off.
Windows is successfully activated, since the system is now running a valid FPP license. The Transition CD 2 is mounted and setup continues. After warnings that his head may explode or his dog may die if the upgrade goes awry, Server2003 R2 setup is run and completed successfully. The Sysop peers at the clock wondering if it is too early to have a beer.
Exit The Sysop stage right
Act V, Scene III: Testing the services
Later Sunday Morning, The Sysop’s House
Enter The Sysop stage right, drinking a water, since it’s still pretty early.
After The Upgrade Process is complete, the spam filtering agency is contacted and the system is taken of Spooling. Test emails are sent to verify connectivity. The Sysop connects to several PC’s in the domain and logs on as an end-user to verify that Group Policy is applying and things like Folder Redirection and drive mappings are occurring. Satisfied that all is operational and working fine, The Sysop pats himself on the back and rechecks the time, which is now 12:01PM. Grinning he rises and walks out.
Exit The Sysop stage right. Moments pass and he returns, with A Beer.
Smiling to himself, The Sysop drinks his beer and logs off all of his sessions. He raises his can and whispers. “The King is dead, long live the King.” He smiles knowing that The Old Server will have new adventures in the weeks to come, being deployed as a minor Duke in a Branch Office, but that, is another story…
Curtain call.
FIN
Subscribe to:
Posts (Atom)
