After a while, I figured there had to be an easier way to get the data without constantly moving an SD Card around. I did some research and found this device:

FYSTEC SD Wifi

After purchasing it and setting it up, I am able to map a drive to it on my windows machine using WebDav. I can then point OSCAR to the WebDav drive instead of the SD Card, and it can read the files directly off of the SD Card inserted into the CPAP machine.

This is the bug we posted for Service Management Automation.  This is a known limitation with SMA and the product team is working on determining if they can change this behavior.

In the meantime, I have developed a runbook that you can run to republish all runbooks in SMA after you make changes.  This runbook loops through every runbook in SMA, exports it, imports it and then publishes it.  It does this 3 times by default, which should cover the situation where you have 3 generations of runbooks.  (Runbook A calls Runbook B calls Runbook C).  You can run this with more iterations if you like; it doesn’t hurt to run it more.

https://connect.microsoft.com/WindowsServer/feedbackdetail/view/917425/sma-child-runbook-not-found-when-starting-parent-runbook-if-runbooks-published-out-of-order

https://connect.microsoft.com/WindowsServer/Feedback/Details/973039

Runbook:

workflow Republish-AllRunbooks
{   
	Param([System.String]$WebServiceEndpoint = "https://localhost", [System.Int32]$iterations = 3)

    InlineScript
    {
		$runbooks = Get-SMARunbook -WebServiceEndpoint $Using:WebServiceEndpoint 

		# SAVE ALL OF THE FILES
		foreach ($runbook in $runbooks)
		{
			Write-Output ("Saving Runbook " + $runbook.RunbookName + "...")
			$definition = Get-SmaRunbookDefinition -WebServiceEndpoint $Using:WebServiceEndpoint -Id $runbook.RunbookID -Type Published
			$path = Join-Path -Path $env:temp -ChildPath ($runbook.RunbookName + ".ps1")       
			$stream = [System.IO.StreamWriter] $path
			$stream.Write($definition.Content)
			$stream.Close()
		}

		foreach ($count in 1..$Using:iterations)
		{
			Write-Output "========== Publish Iteration number $count"
		
			foreach ($runbook in $runbooks)
			{
				Write-Output ("Publishing Runbook " + $runbook.RunbookName + "...")
				$path = Join-Path -Path $env:temp -ChildPath ($runbook.RunbookName + ".ps1")       
				Edit-SmaRunbook -WebServiceEndpoint $Using:WebServiceEndpoint -Path $path -Id $runbook.RunbookID -Overwrite
				$PublishId = Publish-SmaRunbook -WebServiceEndpoint $Using:WebServiceEndpoint -Id $runbook.RunbookID    
			}
		}
    }
}

$myArray = @()
$myArray += Get-WmiObject win32_processor
$myArray.Count

Geting the motherboard manufacturer:

Get-WmiObject win32_computersystemproduct

This returns something like this:

IdentifyingNumber : MXQXXXXXXXX
Name              : ProLiant DL360 G6
Vendor            : HP
Version           :
Caption           : Computer System Product

To view the blog post, go to here: Microsoft “Atlanta” on System Center Operations Manager Unleashed

My first post in a while — but decided I wanted to share new tools I found.

Last week I attended a presentation by two Microsoft employees at my local Dot Net User’s group meeting.  They previewed a new set of tools available for Visual Studio 2010 starting this week.  I couldn’t find these in the extension manager in my copy of Visual Studio yet, but you can go to this page to get the extension:  http://visualstudiogallery.msdn.microsoft.com/en-us/d0d33361-18e2-46c0-8ff2-4adea1e34fef

The Visual Studio 2010 Pro Power Tools include several new features that have been asked for by users:

• Document Well 2010 Plus
  One of the key pieces of feedback that we have received over several versions of Visual Studio is that users want to be able to customize the behaviour of their document tabs.  From the ordering of tabs to the position of the close buttons, user can now configure dozens of different options for their tabs.  Go to Tools -> Options -> Environment -> Document Tab Wellto configure these options as you prefer:
  • Tab Well UI
    • Scrollable tabs
      Maintain spatial consistency of the documents that are included in the document well.
    • Vertical tabs
      Document tabs are shown vertically, allowing you to fit more tabs than are normally visible when shown horizontally.
    • Pinned tabs
      Allows you to pin tabs to keep them always visible and available.
    • Show close button in tab well
      Similar to Visual Studio 2008, will show a close button in the document well that will close the active tab.
  • Tab Behavior
    • Remove tabs by usage order (LRU)
      When a new tab is inserted and existing tabs don’t fit in the document well, instead of removing the tab at the end of the well it will remove the least recently used tab. This ensures that frequently used tabs are readily available.
    • Show pinned tabs in a separate row/column
      Pinning tabs can quickly cause you to run out of space for regular tabs. The option allows you to always show pinned tabs in a separate row (or column, if displayed vertically) from regular tabs.
  • Sorting
    • Sort tabs by project
      Tabs will be sorted by the project they belong to, thus keeping them always together in the document tab well.
    • Sort tabs alphabetically
      Tabs will be sorted alphabetically. When Sort By Project is turned on, tabs will be sorted first by project and then alphabetically.
    • Sort tab well dropdown alphabetically
      The drop down menu at the right end of the document well is sorted alphabetically. This option allows ordering as the tabs are laid out in the document well.
  • Tab UI
    • Color tabs according to their project or according to regular expressions
      This option permits tabs to be colored according to the project they belong to. This is particularly useful when sorting tabs by project, as it allows you to immediately identify different groups of project documents.
      You can also configure regular expressions and assign a color to each one. If the name of a tab matches the configured regular expression, it will be colored with the assigned color.
    • Miscellaneous options that modify tab UI
      • Show document/toolwindow icon in tab
      • Show close button in tab
      • Modify dirty indicator style
        This option allows you to select from a set of different dirty indicators that you might prefer over the asterisk.
      • Modify minimum and maximum tab size
        Allows you to modify minimum and maximum tab size. Try setting minimum and maximum sizes to the same value, and you will have evenly spaced tabs.
• Searchable Add Reference Dialog (one of my favorites)
  The new Add Reference dialog makes it faster and easier for you to find the reference that you are looking for and add it to your VB, C# or F# project.  From the Solution Explorer, simply right click on the References node, select Add Reference.
• Highlight Current Line
  As the resolution of monitors increases, it’s becoming more difficult to find the caret in the code editor.  The highlight current line extension makes it easy to find the caret by highlighting the line that the caret is on in the editor.  You can even configure the default colour by changing the setting for “Current Line (Extension)” and “Current Line Inactive (Extension)” in Tools Options Fonts & Colors.
• HTML Copy
  This extension provides support for the HTML Clipboard format when copying code from the editor.  This means that you’ll no longer have to go fix up the formatting of your code when you paste it into a TFS bug form or any other HTML based control.
• Triple Click
  It’s never been easier to select a line of code from the mouse by simple triple-clicking anywhere on the line.
• Fix Mixed Tabs
  Some developers prefer tabs, others prefer spaces, and nobody likes mixing tabs & spaces.  This extension promotes developer harmony by warning as they are open or save a file that has a mixture of tabs & spaces.  The information bar also provides an easy way to fix the file to suit your preference.
• Ctrl + Click Go To Definition
  This extension gives the editor a web browser by adding clickable hyperlinks to symbols in your code as you hold down the Ctrl key.
• Align Assignments
  This extension is useful for making your code a little more readable by aligning the assignments when you type Ctrl+Alt+] such that it takes this:
  
  And turns it into this:
  
  Please note: This may conflict with your formatting settings. E.g. in C# you will need to disable: Tools->Options->Text Editor->C#->Formatting->Spacing->"Ignore spaces in declaration statements"
• Colorized Parameter Help
  This extension improves consistency with the editor by applying syntax highlighting to the contents of the Parameter Help window for C# &VB.
• Move Line Up/Down Commands
  This extension maps the Alt+Up Arrow & Alt+Down Arrow keys such that they will move the current line of code or the selected lines up and down through the editor.
• Column Guides
  Since Visual Studio 2002, there has been a not so secret registry key which allowed user to draw a vertical line in the code editor.  This is very useful to remind developers that their full line of code or comments may not fit one a single screen. Thanks to this extension this feature has returned with UI configure it.  Simply place the cursor at the appropriate column and select Add Guideline from the context menu

http://wss.made4the.net/archive/2008/11/25/where-to-draw-the-line-between-sharepoint-customisation-and-sharepoint-development.aspx

Error 14274: Cannot delete a job that originated from an MSX server

This error message has two possible causes: either

1. the SQL server is not a standalone server, and this message is appropriate, or
2. the name of the SQL server has changed since the scheduled job was created.

In my case, the scheduled job had been around for over 6 years, and the server had been renamed about 5 years ago.  The job has continued to run and noone needed to make changes to it.

I looked in the sysjobs table in the msdb database and noticed that in the originating_server field, the old server name was still there.  I updated each of them with the following statement:

UPDATE sysjobs SET originating_server='yourNewServerName'

and all was well.

http://cregan.wordpress.com/2006/10/20/moss-2007-sharedserviceprovider-cannot-complete-this-action-error/

Head to Central Administration > Operations.  Under the Global Configuration section, click Alternate Access Mappings.  You will see an entry for http://prod05 (Zone: Default).  Click Add Internal Urls at the top.  Click the drop down next to “Alternate Access Mapping Collection:” and choose the main SharePoint site.  Enter the friendly name into the “URL protocol, host and port” box. (In our case: http://portal)  Make sure you choose Extranet as the Zone.  This is the crucial part.  Leaving the zone as Default will allow SharePoint to serve up the page to that URL, but it will redirect the user’s browser to the unfriendly name.

On the button click or whichever trigger you choose in frmMain, use similar code to this:

// check to see if frmInformation is already open
if (Application.OpenForms["frmInformation"] == null)
{
     // it is not already open, so lets open it and show it.
     frmInformation informationForm = new frmInformation();
     informationForm.Show();
}
else
{
     // it was already open, so bring it into focus.
     Application.OpenForms["frmInformation"].Focus();
}