March 2007 - Posts

MMS2007 Fri 2

Softgrid & SMS 2003

Softgrid Connector for SMS2003; once you have the extension, you can create the package for Softgrid. right-click site database, all tasks: configure Softgrid Virtualization. Configure the service account, the content path, target share name. co-locating the sms distro point w/the softgrid is this. DPContent

Client installer; a package will be created with the msi + switches as defined (or a transform). Version is the version you want to test against.

Configuration; script template directory (vbscripts)

Note: delivery of the app via sms can only be done while a user is logged in. Slated for next release to deliver while no user logged in.

MOF extension for softgrid on myitforum. extend the sms_def.mof to see what softgrid apps are on a computer.

Action Item: install & test

Action items: summarize (as concisely as possible for me) the self-appointed action items from all posts. Provide a timeline to boss of when I'll complete those action items, the benefits of them, and (if approved) resources needed to implement.

In addition to myitforum, another community is http://www.softgridguru.com

This'll be the last entry for MMS2007.

As it has been since my first MMS, when I was such a newbie, the deer-in-the-headlights dazed look was a semi-permanent facial expression that lasted for weeks, I learned so many new things, and have found several self-appointed projects to keep me busy for another year. No amount of webinars, or other training venues ever seem to compare with the breadth and depth of knowledge available at this conference.

Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Fri 1

Advanced Powershell

Well... I've come to the realization that learning powershell by watching advanced powershell scripters isn't going to work out for me. Hopefully in a few months--assuming I get time to play w/Powershell--by the time I get the DVD from the conference, I can re-watch this session, and then I'll get it!

However, at breakfast met two people from the Microsoft PowerShell team--and snagged a business card. She said we could email her anytime with questions.

Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Thurs 6

The block party was lots of fun.

I wonder if they shouldn't have given out "techsexy" t-shirts. Seems to have encouraged some unanticipated results.

IsThisTechSexy.jpg

Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Thurs 5

Powershell & SMS 2003

cmdlets

tools

  1. PowerShell
  2. SMS 2003 SDK (SCCM SDK)
  3. WMI Common information model; CIM Studio
  4. VBScript

Examples of Listing SMS Collections; and how that can be a function, instead of re-creating the snippet over again.

Lots of great examples (like in SMS Recipes). Action Item: grab the powerpoint for the examples

Action item: check out Crimson Editor--they have a free addon for Powershell syntax highlighting.

Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Thurs 4

Ask the experts

  1. ITMU questions (v2 vs v3, plus windows installer hotfix, plus following the kb article)
  2. Question about the flags Yes vs. No at different Primaries. No specific answer; but it could be caused by certain combinations of discovery events.
  3. Question about Software Metering--any plans for a future version to differentiate between an application running in the foreground vs. background? No specific answer, but via Asset Metrix (sms2003 sp3 & sccm); there will be a richer result set.
  4. If an inexperienced SMS Admin accidentally deploys software/advert, what is the quickest way to resolve? Sort of answer: there is no current big red button to "stop" sms. Do not disable the Advertisement--disable the program. That does require a policy update refresh on the clients, so that might not be quick enough. Todd Hemsell suggested removing the gateway address from the NIC on primary sites (MPs). You could still rdp into the server from another server on the same lan.
Posted by skissinger | with no comments
Filed under:

MMS2007 Thurs 3

OSD w/Sccm (vista) part 2

Image Capture:

  1. Automation w/task sequence
    • Wizard
    • Customize/build task sequence to install updates and apps, configure settings
    • advertise that task sequence to reference computer
    • automate install of setup.exe
  2. Driver Catalog: used for 1 image
    • Keep the device drivers separate from the WIM itself--so you can update them seperately during OSD process
    • Drivers Node; drivers are assigned to Driver Packages
    • Two task sequences: auto apply driver (for PnP ones detected) - apply driver (for non-PnP detected, but you know the client will want those drivers
  3. USMT
    • State Migration "Deletion Policy, Delete after setting--so USMT .mig files are automatically deleted after xx days.
  4. Apps installs
    • pre-installed on the image
    • packageid/program (just do it, no conditions)
    • use a task sequence w/variables to determine what to install (packageid/program; i.e., to get Marketing apps)
    • Or... [personal opinion] just use softgrid (who needs locally installed apps?)
  5. note: 1 checkbox for "install all approved updates"--any/all updates approved in SMS for deployment will be installed during deployment.
  6. Migrating from SMS 2003 OSD FP
    • Must uninstall OSDFP before upgrading an SMS 2003 site.
    • Existing deployment packages are preserved, they can use replicated copies in child sites not yet upgraded, can be deleted, but cannot be advertised or modified from SCCM console.
    • images must be recaptures--you cannot use existing images.
    • sms 2003 clients will reject task sequence ads--clients must be sccm clients
  7. If using BDD 2007 moving to Sccm07, whitepaper coming on migrating custom actions developed for BDD into sccm07

Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Thurs 2

SCCM SDK (Software Development Kit)

Themes/goals of this SDK

  1. Retain existing functionality from sms2003 to support existing customer/partner solutions
  2. Enhance so partners/customers can do even more
  3. Simplify docs, scenarios, samples

What's new:

  1. documentation more "how-to"
  2. improved code snippets
  3. c# and vbscript snippets
  4. moving toward a continuous publishing model so SDK can be updated more frequently (hey! I recognize this recommendation from last year's BOF on documentation!)

What's changed:

  1. Right-click tools (obviously) won't work because the UI has changed from MMC 2.0
  2. Managed Site Server interfaces won't work (c# libraries)
  3. no Powershell in the initial version of the SDK; but future flavors will.
  4. MP API very different because of security changes
  5. New layer; Managed Provider Interfaces (could functions to make job easier)
  6. Admin UI Plugin1 (XML) to get right-click actions back; must use managed code for Admin UI extension
  7. Admin UI Plugin2 (XML)

Site Servicer Interfaces

  1. Add actions (right click)
  2. Add property pages (tabs)
  3. Add forms (collection of tabs)
  4. add new wizard
  5. add navigation nodes (sub nodes) Note: keep new subnodes under the Tools node
  6. create new views (the right pane); even new home pages

Demo of grabbing the Packages Node Guid, looking at the XML for the right-click actions available for the packages node.

Note: if you are going to add a right-click to a specific report, use the report guid as the target, not http://whatever/smsreporting_123/report.asp=...

Careful: don't modify the default files for the admin ui, sdks, etc.

Client interfaces

  1. Exposes the control panel applet functions (hmm.. probably just wait for Roger Zander to update his Client Center w/the new functions for DCM, Software Update Management)

OSD w/the SDK

  1. Allows for additional of custom 3rd party actions that behave like the built-in ones - instead of just the run command line option. Seamless integration with Task Sequence Editor.

DCM w/the SDK

  1. Theoretically, a company would provide a provider for their product, to allow you to do DCM for settings in their product.

Software Updates w/the SDK

  1. System Center Updates Publisher - lets ISVs/SIs/OEMs and customers create and deploy custom updates.

Software Distrib

  1. Branch DPs, Maintenance windows, WOL
  2. Improved how to documentation
Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Thurs 1

General Session

Puppies Are Adorable. Sorry, you had to be there.

Panel Discussion: Robert Fort: Virgin Entertainment; Takis Petropoulos, Dell, Rodney Orange, Carnival Cruise Lines, Jack Story EDS

They discussed their implementations of SCOM and SCCM

Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Wedn 5

It's all about social/meeting peers.

After dropping the laptop & stuff back at the hotel, went to the expo center to chat w/SMSexpert (great bunch, and great products, too, check 'em out) and be close enough for the xbox drawing to hear my name just in case I won (didn't) and also so I wouldn't get lost trying to find the SMSExpert party boat, I heard Ron Crumbaker do a very classy thing.

If you've been following the MMS events vicariously, you've heard that the MyITforum booth was mobbed Monday night by hundreds of people trying to pick up a button for the Tuesday night MyITForum party (I was in the mob, too!) And the MyITForum booth has continued to be hopping with people asking Ron to sign their copy of his book, or just thanking them for a great site.

What may not have been reported was I've heard the other vendors at the expo were left wondering--why is this booth so popular? Their swag doesn't flash/light up, or have mints inside, or... Especially the vendors immediately around the MyITForum booth, and although there is lots of people traffic, many are going to the Myitforum booth. So while everyone was hovering around for the Xbox drawing, Ron asked the crowd to check out the vendors in the immediate vicinity; pointing out that some of those vendors also had Xbox raffles; so if you don't win this one--sign up over there, too, for a chance at one.

This next comment may be completely off the mark--but I'm hoping that the other vendors noticed the mad dash for MyITForum party--and perhaps help fund the party next year. Doing so may alleviate two issues seen this year; the party could be maybe 20-30% larger (I don't think I'd personally want it much bigger--you'd lose the intimacy of a smallish gathering, it was over 200 people already) and the buttons could be known to be offered at multiple booths--increasing the chances of people looking for the buttons to snag one. (I may be wrong on this, too, but I believe the buttons were available at multiple booths, like Microsoft's; but when they saw the craziness Monday night they gladly returned their bunch of buttons to the Myitforum booth to hand out.)

I think that would be "TechSwarmy"

What's TechSwarmy you ask? After some debate (alcohol was involved), a small consensus (<10 people) decided that since Sales & Marketing people could create their own words to describe something (TechSexy)--so can we. I may not recall exactly the correct pronunciation or spelling, but it's a combination of attemping to include Sales and Marketing into the word: TechSwarmy. I apologize to those present creating the new word if I've missed the mark on spelling. It might have been TechSmarmy (Todd, Angie, Mike, John, and others; including some MS people--who for the record were not participating in the making up of the new name)

Another suggestion for next year that may help w/the MyITforum party. Assuming that the others' goal for attending the party was the same as mine (to increase my chances of meeting all of the people who've helped me out on the forum and lists), how about an email list that is only active from the Wednesday before (to allow the people who have the 24+ hour travel times from across the world) and goes away the Sunday after MMS. The email list would be solely for "A bunch of us are meeting in the lobby of Hotel xyz at 7pm going to the wherever club; meet us if you are interested" The list could be promoted at the booth during the conference, too. Since everyone seems to have email with them wherever they go; they could join the list from their PDA right there if they were new to the conference/Myitforum and were interested, too.

Other social: went for a cruise in the bay on the SMSExpert Party Boat. It was a very nice ride--got to see a lot of the skyline, the Maritime museum from the water side, a very nice sunset; and oh, yeah--met lots of more wonderful people.

Thursday heads up: the "big" party is tonight. It's "Block Party at the Gaslamp Quarter", with an outdoor stage for "Lavay Smith and Her Red Hot Skillet Lickers". A co-worker from our San Diego office will be joining me using the optional guest pass--I think that'll make it twice as fun!

Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Wedn 4

SCCM07: deploying Windows in the Enterprise: part 1

Deployment scenarios

  1. New machine
    • fresh out of the shipping box
    • reimage existing machine for new user
  2. Wipe-and-load
    • upgrade OS on existing
    • reinstall apps after upgrading OS
    • USMT (before the OS upgrade, after reinstalling apps)
  3. Side-by-side
    • Similar to wipe-and-load; but usmt settings .MIG file isn't local 'cause the data is moving
  4. In-place migration
    • upgrade OS on existing
    • migrate installed apps
  5. offline w/removable media
    • using dvd/usb/cd set because of low bandwidth considerations
    • no status reporting
  6. PXE boot
    • integrate with WDS PXE servers
    • control deployment actions w/SCCM ads
    • self-provisioning w/F12 or fully hands off datacenter

SCCM new objects to support OSD

  1. The OS image (.WIM) itself
    • using SCCM Distro points, and the (optional) binary delta replication
    • Image Properties
      • # of images in the WIM file, image sizes, disk layout, etc.
      • properties read/written directly to/from the WIM file
      • provider computer must have read to the Wim, write to do updates.
  2. Boot Image
    • WinPE 2.0, even when deploying an older OS, bootable WIM format
    • replicated to DPs and PXE servers
    • x86/x64 boot images from WAIK (can customize)
  3. The Package
    • contains the files from the original install cd (i.e., where setup.exe lives for doing a next/next finish install.
      • Why? for building your reference computer using next/next/finish, or the occasional (hopefully one-off) setup.exe builds
    • replicate to all DPS, all SCCM Sites.
  4. Task Sequences are "techsexy".
    • Off topic note: after some debate (alcohol was involved), a small consensus (<10 people) decided that since Sales & Marketing people could create their own words to describe something--so can we. I may not recall exactly the correct pronunciation or spelling, but it's a combination of attemping to include Sales and Marketing into the word: TechSwarmy. I apologize to those present creating the new word if I've missed the mark on spelling.
    • Back on topic now
    • Task Sequences are policies
    • Internet-facing clients are excluded
    • 2 types of actions for TS
      • Built-in
      • Custom (vbscript, any other kind of command line)
    • Grouping and logic; lots of logic built around the steps, continue on error, grouping of tasks, conditions that need to be met (OS ver, regkey exists, that type of thing)
    • Variables -- things like the license keys for software, passwords for joining the domain, are obfuscated for security

Reporting

  1. Reporting based on status messages; not State. Status messages are sent from each policy step in the task sequence; like "success", "failed because" or "skipped because logic/condition not met [os ver, reg key]
  2. Local client log for Task Sequencing: smsts.log

Task Sequencing is not just for OSD; you can sequence anything. Right now we do some chaining of applications (the Marketing apps, or the IP apps, where the core app needs to be installed first, then the 3rd party add-on app after) It sounds like chaining of applications could be replaced with Task Sequencing

Action Item: SCCM Beta 2 in the lab, recreate the existing chained apps via existing package/program/run this program first; duplicate using Task Sequencing

Now the expo was less crowded, stopped at the Quest booth for a demo of PowerGui for Powershell. It's a free tool, looks great. I think that will be a better way for me to learn PowerShell (I've gotten to page 8 in the book I bought. Does it count that the book is on the coffee table at home and theoretically I can read more anytime? Or should I just face reality and accept that if I've only gotten to page 8 in 2 months--time to look for other methods to teach myself Powershell...)

Action item: setup PowerShell & PowerGUI, and start playing. Let co-worker know about PowerGUI (who also expressed interest in learning PowerShell), and if I play my cards right... convince him to learn PowerShell first--and then teach me. I believe he can be bribed w/chocolate chip cookies [let me know, Ryan, if bribery will work].

Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Wedn 3

SCCM2007 Desired Configuration Manager

  1. .net 2.x
  2. SML (Service Modeling Language): built on XML
    • structure: objects & relationships
    • desired config
    • admin policies
    • events; rules
  3. Compliance results sent as xml attachments to state messages; then use query-based collections to push out a software distribution that will put the client back into compliance--whether that is a repair of the application, a script, etc.
  4. Parent/Child relationships when authoring Configuration Items. i.e., the base configuration baseline from MS; if MS released an updated baseline, you do not have to re-build whatever content you've added/changed if you've done a child CI
    • Parent CI is
      • Imported from MS
      • Defined core settings
    • Child CI is
      • inherit from parent
      • add rules
      • add new settings for this child only
    • Duplicate CI
      • i.e., cloned from an original, full editing capabilities, no link back to the original
  5. Configuration baseline: buch of CIs required/optional/prohibited

Action Items: check out SML: http://www.microsoft.com/windowsserversystem/dsi/serviceml.mspx

Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Wedn 2

WSUS 3.0

Action items: see where the internal team is on WSUS 3.0 Work w/them for future integration of existing wsus w/future implementation of sccm2007

Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Wedn 1

Keynote: Kirill Tatarinov, "Driving to Dynamic IT"

Model based policy. Automation. Embedded Knowledge.

  1. Dynamic Configuration Management
    • Deep Insight into Assets (Asset Intelligence in sms2003 SP3)
    • Adaptive software distribution (softgrid / term serv / vpc)
    • compliance to desired state
  2. Dynamic Operations Management
    • Holistic health monitoring
    • Optimize and protect the physical & virtual
    • Proactive problem resolution
  3. Dynamic Service Management
    • platform for connecting and automating IT
    • optimize asset use & minimize risk
    • deep insight to improve decision-making ability

SCCM07 highlights

  1. "Live" asset intelligence
  2. Auto OS image Mgmt & deployment
  3. simplicity (reduced # of clicks in the console)
  4. Intel AMT integration (connecting Active Management Technology w/SCCM)
  5. Dell, HP, and IBM update catalogs
  6. Desired Configuration Mgmt

Demo on Desired Config Mgmt

Configuration Out of Compliance State, using Office 2007 professional as the example, and if your enterprise settings are (for example) things to do with OST/PST settings, you can create a collection of non-compliant computers, and then basically Repair the MSI on the client to reset OST/PST settings to those configured in the MSI.

SCOM2007 highlights

  1. end-to-end service mgmt
  2. deep ms knowledge (cooperative work w/in MS for FPs for SCOM, and 35 partners announcing solutions at MMS connectors, extensions, etc. for OM)
  3. automated problem resoloution ("do it" button)
  4. scalability
  5. secured role-based access
  6. expanded partner ecosystem

Announcement: System Center Data Protection Manager 2007 Beta 2 within 30 days

Announcement: System Center Virtual Machine Manager 2007 Beta 2

Announcement: System Center Service Manager Beta 1 within 45 days

demo of SCSM:

  1. After the end user requests (for example) Visio, there is a Vista System Center Gadget for the end user to know what (if anything) is for me--like an unapproved request for Visio is hanging out in workflow, waiting for my boss to approve the license.
  2. Also a demo of a battery recall. Kind of generic (just looked for all laptops by manufacturer XYZ, not laptops by manufacturer xyz with battery model ZYX), but still highlighting how SMS asset info is available to SCSM.

Projected release dates

  1. Config Manager H2 2007
  2. Virtual Machine Man H2 2007
  3. Data Protection Man H2 2007
  4. Service Manager will be H1 2008 (probably will be the star at MMS2008)
  5. Ops Man (the next version I think) H2 2008
Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Tuesday 5

It's all about socializing... the MyITForum party was a great meet 'n greet. Met lots of people from the lists and forums.

I also received an award: a Transformer! It's kind of cute. I'll have to put it on my desk.

Received several 'thank you' for the TZUpdater for DST/sun java article. It helped out at least 4 people during early March!

Also heard a couple war stories about DST & SMS in general. Although the DST updates, revisions, etc; were confusing, using SMS they were able to get the updates out and verified (advert status reports or add/remove programs patch exists)

Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Tuesday 4

Ron Crumbaker, Web Remote Tools


Why do I need it?

  • Web based tool for SMS admin; Console Functions; portable. Better control over what functions are used by true non-admins (Helpdesk)
  • Many tools within one application
  • users/companies asks for it, but MS does not have a web console.

History:

  • Screenshots of v2.9; some history about editing the 10 lines in the 189 lines of code. Occasionally; people messed up...
  • Screenshots of v3.21, a few more controls; a little better filter. 21 lines of code to edit. Occasionally; people messed up...
  • Screenshot of v3.29 (beta; 2 people tried it; added some WOL) Added
  • Screenshots of Chris Stauffer's edits, my edits.

v4: new functions; closer console replacement tool.

Announcement: Web Remote Tools v4 has a name change: SMS Web Essentials v4.02 (in a few months, probably System Center Web Essentials v4.02)

Total re-write in ASP.net & AJAX; integrated with SMS Experts Companion for WOL. Configuration/Setup section. Seamless upgrade setup options.

Demo:
6 tabs: Remote Admin, remote Manage, system maintenance, install software, user info, User info, Collection Admin (add machine to any collection)

New stuff: v4.03 will have "themes" (so you could change colors).

v4.02: Upgrade function built in; so if you add content to your own page that you think may benefit others; email Ron with the code; and he'll put it in an upgrade (if applicable)

Release date: "as soon as feasibly possible"--which he's guessing will be 2-4 weeks.

v4.03, 4.04 to better integrate w/System Center products.

Question: Jitter (never heard this term before; but I think he meant staggered installs, i.e., 500 clients; stagger the install to 50 a time so as not the kill the network). Wanted to know if it could be an enhancement.

Answer from the floor (another user): SMSExpert's Load Companion. Wouldn't be part of SMS Web Essentials 4.x; but it would be something for this person to look into. Also "Trickle Feed" script, the code is in the Code Repository; posted by Rick Jones

Announcement: new Code Repository soon.


Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Tuesday 3

SCCM2007: state of the union

Catch phrase "techsexy", using some funny pictures of what is not "techsexy" vs. what is (5 gear items hanging on your belt vs. a gear jacket w/all your gear tucked in pockets--and some more pictures that perhaps hovered on the edge of good taste...

Announcements: SP3 'real soon', tons of asset reports

Demo'd some of the features of SCCM2007's admin console; several slides on the new things in sccm. Stressed that with internet facing clients; as an SMS Admin I'll need to know more about PKI and certificate authority.

Action Items: SCCM2007 Beta 2 eval CD was in the bag given out--asked us to "kick the tires"

Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Tuesday 2

Keynote, Bob Muglia

Title: Delivering on Dynamic Systems.

Taked about industry trends, known product releases.

  1. Virtualized Infrastructure
    • Virtual Server (OS)
    • Softgrid (App Layer)
    • Terminal Services (Presentation Layer)
  2. Design for operations
    • Visual Studio
  3. Knowledge drivement management
    • System Center
    • MS Office
    • ITIL/MOF; SCOM, SCCM, Incident & Problem Management, Asset Lifecycle Management, Change Mgmt
      • Knowledge
      • Self-service portal
      • CMDB
      • Workflow
  4. Service Manager, Ops Man, Config Manager, VM Manager, Data Protection Manager (System Center Essentials for <50 servers, <?? clients)

http://www.microsoft.com/io (Optimizing your Environment); moving from basic, to standard, rationalized to Dynamic

Next versoin of server "Longhorn", stressed the virtualization features built into it.

Demo: Windows Virtualization; demo-ing Longhorn. Server Core is just a command line interface. Mentioned Longhorn is the 'perfect' time to migrate to x64. 8 (yes 8) virtual CPUs available to virtualized machines.

Demo: SCOM2007

Video: how Carnival Cruise Lines uses SCOM.

Announcements:

1. EMC, Cisco, and Microsoft: Industry Commitment to "core models". Foundational work that will be transformed into industry standards. He stressed there will be more companies, but these are the 3 right now.

Cisco video: Management of IT Infrastructures. Standard way to monitor Servers, apps, networking, and storage devices. The open functionality of the models will reduce complexity... Customers will be able to understand when it is operating efficiently, and address when it is not running efficiently.

2. System Center Operations Manager 2007, next week (got a 120day eval cd)

3. EMC: end to end service visibility and control. EMC Smarts; model based management. Shift burden of managing complexite from user to system. Return behavrioral line of sight to IT operations. Fast accurate root cause across systems infrastructure, ensure availability of critical business services. Discovery & Health monitoring for the next version of SCOM. "SMARTS". OM will provide the core infrastructure for SMARTS analysis to help.

Essentially: an EMC Smarts bi-directional connector for SCOM; collaboration via shared behavioral modeling language. (this is for current SCOM); future versions will expand on this.

Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Tuesday 1 SMSExpert # 145

Shameless shout out: if you are at MMS, and you read this blog while at MMS, and you happen to have the matching number for the SMSExpert swag of 145 (which is my #), send me an email, or setup a Meeting Place appointment with me!

Posted by skissinger | 1 comment(s)
Filed under:

MMS2007 Monday

I'm going to try to blog about MMS2007. Last year, when I sent my daily updates to the boss and coworkers, they called it "an interesting and slightly scary peek into Sherry's mind". I referred to my updates as a 'stream of consciousness'. So be warned; some of this may make absolutely no sense out of context. I'll probably have a rough time interpreting what I meant in a few weeks!

Conference Events

  1. Self-Paced Hands-on-lab; ended up doing a bit of Custom Update Tool for SMS2003, then did Deploying MS updates w/Sccm2007.
  2. Demystifying SQL (2 sessions, quick 'n' dirty summary of what I picked up as key points of things I didn't know, or clarified points)
    • when making your own view, use a prefix unlikely to be used by MS or others, i.e., v_Unique_SummaryOfView
    • dbo should own the stored procedure (sp_) to prevent potential broken ownership chains
    • Backup your views & sp's: SQL Enterprise Mananger, Create Script Tasks, General SQL Script; Show All, check on All Views, and All Stored Procedures; Options, check Script Object Level Permissions, Windows text, 1 file.
    • in general, avoid negative logic, may to a full table scan. Avoid a view based on a view
    • In QA, "Show Execution Plan" to check for index usage & table scans.
    • SQL Profiler Utility
    • declare a variable in an sp_.... @CollectID varchar(8), then in the statement use where v_fullcollectionmembership like @CollectID. Then, when using in a web report, use Exec sp_Unique_WhateverYouCalledIt @CollectionID; and a prompt of CollectionID

Action Items

  1. Grab the labs, Powerpoints, examples
  2. SQL Server Books Online (BOL). I believe this is already in SMS as a package for the web developers. I can just request it for my machine--it's free; so it's just a matter or recording it & getting it advertised.
  3. Review Chap 11 for SMS 2003
  4. Play w/creating my own views and stored procedures in the lab, then if useful/productive, port to production.

Expo/vendors

I'm familiar with most of the players from the last several years--they advertise all over myitforum so no need to repeat them here; but there were a few new ones that caught my eye. Maybe they were there last year, too--or maybe this year I'm just more receptive to them. Anyway... web sites to follow up on, learn more about, etc.

  1. www.powergadgets.com their tag line is "Desktop Reporting and Monitoring for IT/DB Professionals...who don't write code". Hey, if they've already written it, why should we reinvent the wheel?
  2. Quest software's PowerGUI (I think it's for PowerShell? too crowded to really look; I'll have to go back)
  3. NetCmdlets: www.nsoftware.com/powershell (Note to self: in the bag'o'swag: "visit us at booth #124 to get a free license"--I'll have to stop and let them swipe my card)

Social

Got reacquainted (or acquainted for the first time face-to-face) with Myitforum'ers, and just people I've met at previous conferences. The opening party (the Expo) was packed, and the MyItForum booth was just insanely buzzed with hundreds of people all trying to get into the party! (got my button, whew!) But the Myitforum booth wasn't the only buzzing booth--the entire expo center was wall to wall people--true, there was free food, beer, and wine, but in between all of that people were checking out the vendors, and making contact with Alumni and first-timers everywhere.

Tuesday Preview: actually I'm double and triple booked on a several sessions. Not sure which ones I'll actually end up attending, and which I'll just download the slides. But I know I'm going to the Lab for HW Inv (Jeff Gilbert), and Ron Crumbaker's Web Remote Tools v4.

Posted by skissinger | 1 comment(s)
Filed under:

Confirm DST2007 Regkey for a specific computer interactively - RCrumbaker Web Remote Tools 3.21

The boss asked for a button on the Web Remote Tools page so that local techs could run a quick "is it patched" during the next few weeks to quickly eliminate any questions about problems that *may* be reported and trying to associate whatever that problem may be with an unpatched computer.  I'll probably yank this button off the page in April; but if anyone else is interested... 

Edit MachRest.asp, and add a button by your other buttons (about line 80-ish):
<INPUT id="Button730" style='WIDTH: 180px' type='button' value='Confirm DST Fix' name='Btnl730'>

Then copy/paste the below (the Sub) probably near the bottom, just before the </script>, after all of the other SUB/end Sub routines.  In the attached sub routine, change the "YourSMSServerNameHere" to match your SMS server name. 

Sub Btnl730_OnClick
On Error resume next
 Set sho = CreateObject("WScript.Shell")
 CompName = trim(document.frmMain.txtValue.value)
 if len(trim(CompName)) = 0 Then
              MsgBox "Computer Name or IP required",,"Confirm DST Fix"
            Else
             Set WShell = CreateObject("WScript.Shell")
  Set objPing = GetObject("winmgmts://" & "YourSMSServerNameHere" & "/root/default:PingPoller")
  objPing.Ping Compname, "100", "1", PingResult
  if PingResult <> 0 then
   msgbox "Machine did not respond to ping.",,"Confirm DST Fix"
  Else

 dim strRegValue(100)
 dim strRegValue2(100)
 Const hRegTree = &H80000002
 Set objReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & _
   CompName & "\root\default:StdRegProv")
   strRegKey = "SYSTEM\CurrentControlSet\Control\TimeZoneInformation"
    strRegDataType = "BINARY"
    strRegValueName = "DaylightStart"
      intResult = objReg.GetBinaryValue(hRegTree, strRegKey, strRegValueName, strRegValue)
    strRegValueName2 = "StandardStart"
      intResult2 = objReg.GetBinaryValue(hRegTree, strRegKey, strRegValueName2, strRegValue2)

 If strRegValue(2) <> 3 Or strRegValue(4) <> 2 Or strRegValue(6) <> 2 Then
    i=1
 end if
 If strRegValue2(2) <> 11 Or strRegValue2(4) <> 1 Or strRegValue2(6) <> 2 Then
    i=i+1
 end if
 select case i
   case 0
     strComment = "Success Indicated"
   case 1
     strComment = "Inconsistent Results"
   case 2
     strComment = "Failure: Values do not match expected"
   case else
     strComment = "Inconsistent Results"
 end Select
MsgBox CompName & ": " & strcomment,vbOKOnly,"Confirm DST Fix"
            end if
end If 
 
End Sub

Posted by skissinger | with no comments

One Method to confirm DST 2007 changes

For some operating systems, the DST fix is essentially a registry key import. This outlines one method of reporting on specific elements within the SYSTEM\CurrentControlSet\TimeZoneInformation, DaylightStart and StandardStart Registry keys.

A bonus is that since the official hotfixes also modify these registry keys to the same values, reports will not have to be OS-specific.

Advertise the attached VBScript to your computers (rename from .txt to .vbs). To get updated data, the advertisement will need to be on a recurring schedule. For example, if you target non-compliant machines with the hotfix (or to re-run the reg import), you will also need to re-run the vbscript to populate WMI, and then the next Hardware Inventory will report (hopefully) success.

Add the reporting class to your sms_def.mof on the server (or mini.mof, if that's what you do), and compile the changes on your clients.


MOF addition:
// <:[-<>>>>>>Start>>-DST2007 RegTimeZone-<<Start<<<<<<<<>=]:>

#pragma namespace("\\\\.\\root\\cimv2\\sms")

[SMS_Report(TRUE), SMS_Group_Name("DST2007 RegTimeZone"), SMS_Class_ID("MICROSOFT|SMS_RegDST2007|1.0")]

class SMS_RegDST2007 : SMS_Class_Template
{
[SMS_Report(TRUE), Key] string Comment;
[SMS_Report(TRUE)] Uint32 DaylightStart3;
[SMS_Report(TRUE)] Uint32 DaylightStart5;
[SMS_Report(TRUE)] Uint32 DaylightStart7;
[SMS_Report(TRUE)] Uint32 StandardStart3;
[SMS_Report(TRUE)] Uint32 StandardStart5;
[SMS_Report(TRUE)] Uint32 StandardStart7;
};
// <:[-<>>>>>>End>>-DST2007 RegTimeZone-<<END<<<<<<<<<>=]:>


You'd write reports against the new v_gs_SMS_REGDST2007 view

Credits: Matt Broadstock for the vbscript snippet!

Posted by skissinger | with no comments
Filed under: ,