Chris Stauffer at myITForum.com

 http://www.zune.net/en-us/support/zune30.htm

 Just incase the link doesnt work for you here is what it says:

*********************************************************************************

  Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;}

My Zune 30 is frozen. What should I do?

Follow these steps:

1. Disconnect your Zune from USB and AC power sources.
2. Because the player is frozen, its battery will drain—this is good. Wait until the battery is empty and the screen goes black. If the battery was fully charged, this might take a couple of hours.
3. Wait until after noon GMT on January 1, 2009 (that's 7 a.m. Eastern or 4 a.m. Pacific time).
4. Connect your Zune to either a USB port on the back or your computer or to AC power using the Zune AC Adapter and let it charge.

Once the battery has sufficient power, the player should start normally. No other action is required—you can go back to using your Zune!

My Zune 30 has been working fine today. Should I be worried?

Nope, your Zune is fine and will continue to work as long as you do not connect it to your computer before noon GMT on January 1, 2009 (7 a.m. Eastern or 4 a.m. Pacific time).

Note: If you connect your player to a computer before noon GMT on January 1, 2009,  you'll experience the freeze mentioned above—even if that computer does not have the Zune software installed. If this happens, follow the above steps.

What if I have rights-managed (DRM) content on my Zune?

Most likely, rights-managed content will not be affected by this issue. However, it's a good idea to sync your Zune with your computer once the freeze has been resolved, just to make sure your usage rights are up to date.

What if I took advice from the forums and reset my Zune by disconnecting the battery?

This is a bad idea and we do not recommend opening your Zune by yourself (for one thing, doing so will void your warranty). However, if you've already opened it, do one of the following:

• Wait 24 hours from the time that you reset the Zune and then sync with your computer to refresh the usage rights; or

I got up for the start of my vacation this morning to find that my wife’s Zune was dead. After taking it apart to see if something was just hung (wanted to remove the battery to restart it since nothing else worked) I told her that it looked like it was dead and that I would have to get her a new one. But I just bought a new laptop so it will have to be a little bit till I can afford to get her another one.

So anyway I am playing with my new Dell Studio 15 laptop and watching the news. I had to rewind the news when I heard the presenter say that all ZUNE 30’s where dead as of 12am. So I quickly grabbed my zune 30 and sure enough it was dead as well.

This sucks because we are headed to the in-law’s this weekend and my zune is my sanity check. Well at least I have the new laptop to play with :-)

Places tracking the zune 30 issue

Engadget: [ 30GB Zunes Mysteriously Begin to Fail ]
Gizmodo: [ All Together Now!: 30GB Zunes Failing All At Once ]

Zune Support:

http://www.zune.net/en-US/support/default.htm

We found a small issue with the new code.

Apparently some of the laptops have wireless cards that are active (actively looking for a connection) and reporting an address of “0.0.0.0”

When the query ("Select IPAddress from Win32_NetworkAdapterConfiguration where IPEnabled=True") is run these machines report the wireless card as enabled so when the script does the loop it keeps the last Ipaddress in the array. This was causing the remote tool to fail because the last value was 0.0.0.0

I added an “if” statement that will only act upon addresses that are greater than “0.0.0.0” this resolved the problem in testing.

I also added an “Exit Sub” to the “If” statement so it should stop looking as soon as it finds a IP Address, so if the machine has 2 nics with 2 addresses it should only try and connect to the first address that it comes to that is not “0.0.0.0”

I Also cleaned up some extra lines that where not needed.

Here is the new code:

**********************************

Btnl_OnClick

Sub Btnl_OnClick
    On error Resume Next
    Dim CompName,oWshShell
    CompName = Trim(document.frmMain.txtValue.value)
    pathA = "\\{SCCMServer}\remote$\remote.exe"
    pathB = "\\{SCCMServer}\remote$\rc.exe"

    If len(Trim(CompName)) = 0 Then
                        MsgBox "Please type a Machine Name.",,"SCCM 2007 Remote Control"
    Else
        Set oWshShell = CreateObject("WScript.Shell")
        set IPConfigSet = GetObject("winmgmts:{impersonationLevel=impersonate}!//"& CompName &"").ExecQuery("Select IPAddress from Win32_NetworkAdapterConfiguration where IPEnabled=True")
        If Err.Number <> 0 Then
        MsgBox "Machine Not Found on the network, Please check the name and try again.",48,"SCCM 2007 Remote Control"
        Err.Clear
         Else
            for Each IPConfig in IPConfigSet
                If Not IsNull(IPConfig.IPAddress)  Then
                For i=LBound(IPConfig.IPAddress) To UBound(IPConfig.IPAddress)
                StrIP= IPConfig.IPAddress(i)
                If  StrIP > "0.0.0.0" Then
               ‘ MsgBox "Machine's IPAddress: " & StrIP ,48,"SCCM 2007 Remote Control"
            Set objSWbemServices = GetObject("winmgmts:\\" & CompName & "\root\cimv2")
            Err.clear
            Set colSWbemObjectSet = objSWbemServices.ExecQuery("Select * FROM Win32_OperatingSystem")
            For Each objSWbemObject In colSWbemObjectSet
            StrOS= objSWbemObject.Version
            Next
            ‘MsgBox "Machine's OS: " & StrOS ,48,"SCCM 2007 Remote Control"

      If StrOS = "5.0.2195" Then
        'You will need To edit the following line to fit your environment.  SMSServer = Your SMS Server Name
             oWshShell.run pathA & " 2 " & CompName & " \\{SCCMServer}\",0,False
             Exit Sub
        Else
               oWshShell.run pathB & " 1 " & CompName & " \\{SCCMServer}\"
          Exit Sub
      End If
                End If
                Next
            End If
Next
End If
    end If
End Sub

*********************************

Let me know if anybody finds any additional issues.

We found a small issue with the new code.

Apparently some of the laptops have wireless cards that are active (actively looking for a connection) and reporting an address of “0.0.0.0”

When the query ("Select IPAddress from Win32_NetworkAdapterConfiguration where IPEnabled=True") is run these machines report the wireless card as enabled so when the script does the loop it keeps the last Ipaddress in the array. This was causing the remote tool to fail because the last value was 0.0.0.0

I added an “if” statement that will only act upon addresses that are greater than “0.0.0.0” this resolved the problem in testing.

I also added an “Exit Sub” to the “If” statement so it should stop looking as soon as it finds a IP Address, so if the machine has 2 nics with 2 addresses it should only try and connect to the first address that it comes to that is not “0.0.0.0”

Here is the new code:

**********************************

Sub Btnl_OnClick

On Error Resume Next

          Dim CompName,oWshShell

          CompName = trim(document.frmMain.txtValue.value)

          path = "\\{SMSServer}\remote$\remote.exe"

          If Len(Trim(CompName)) = 0 then

                    MsgBox "Please type a Machine Name.",,"SMS 2003 Remote Control"

          Else

                    Set oWshShell = CreateObject("WScript.Shell")

                    set IPConfigSet = GetObject("winmgmts:{impersonationLevel=impersonate}!//"& CompName &"").ExecQuery("Select IPAddress, IPSubnet  from Win32_NetworkAdapterConfiguration where IPEnabled=True")

                    If Err.Number <> 0 Then

                    MsgBox "Machine Not Found on the network, Please check the name and try again.",48,"SMS 2003 Remote Control"

                    Err.Clear

                    Else

                              for Each IPConfig in IPConfigSet

                                        If Not IsNull(IPConfig.IPAddress)  Then

                                        For i=LBound(IPConfig.IPAddress) To UBound(IPConfig.IPAddress)

                                        StrIP= IPConfig.IPAddress(i)

If  StrIP > "0.0.0.0" Then

                                        'MsgBox "Machine's IPAddress: " & StrIP ,48,"SMS 2003 Remote Control"

                                        'You will need To edit the following line To fit your environment.  SMSServer = Your SMS Server Name

                                        oWshShell.run path & " 2 " & StrIP & " \\{SMSServer}\",0,False

Exit Sub                                    

End If

                                        Next

                              End If

Next

End If

          end If

End Sub

*********************************

Let me know if anybody finds any additional issues.

Here is the code to fix the web console issue in SCCM 2007 talked about in the previous blog

'************************
' Remote Control Button *
'************************

Sub Btnl_OnClick
'You will need to edit the following line to fit your environment.  SCCMServer = Your SCCM Server Name
    On error resume Next
    Dim CompName,oWshShell
    CompName = Trim(document.frmMain.txtValue.value)
    If len(Trim(CompName)) = 0 Then
                        MsgBox "Please type a Machine Name.",48,"SCCM 2007 Remote Control"
    Else

        Set oWshShell = CreateObject("WScript.Shell")
        set IPConfigSet = GetObject("winmgmts:{impersonationLevel=impersonate}!//"& CompName &"").ExecQuery("select IPAddress from Win32_NetworkAdapterConfiguration where IPEnabled=TRUE")
        If Err.Number <> 0 Then
        MsgBox "Machine Not Found on the network, Please check the name and try again.",48,"SMS 2003 Remote Control"
        Err.Clear
         Else
            for each IPConfig in IPConfigSet
                if Not IsNull(IPConfig.IPAddress) then
                for i=LBound(IPConfig.IPAddress) to UBound(IPConfig.IPAddress)
                StrIP= IPConfig.IPAddress(i)
                'MsgBox "Machine's IPAddress: " & StrIP

                Next
            End If
next

        Else   
            Set objSWbemServices = GetObject("winmgmts:\\" & CompName & "\root\cimv2")
            err.clear
            Set colSWbemObjectSet = objSWbemServices.ExecQuery("Select * FROM Win32_OperatingSystem")
            For Each objSWbemObject In colSWbemObjectSet
            StrOS= objSWbemObject.Version
            Next
        end If
    end If

    If StrOS = "5.0.2195" Then
        Set oWshShell = CreateObject("WScript.Shell")
        path = "\\{SCCMServername}\remote$\remote.exe"
        'You will need to edit the following line to fit your environment.  SMSServer = Your SMS Server Name
         oWshShell.run path & " 2 " & StrIP & " \\{SCCMServername}\",0,False
         Else
            Set oWshShell = CreateObject("WScript.Shell")
            path = "\\{SCCMServername}\remote$\rc.exe"
             oWshShell.run path & " 1 " & StrIP & " \\{SCCMServername}\"
            end If
End Sub

There has been an on going issue with the SMS Web console that has existed since the page was created back in 2004.

For some reason certain machines would report back that they did not respond to a ping even though the ping function was working when you clicked the Start Remote Control button. This would cause the button to fail and would not allow the tech to use remote control.

This was a flaw is the DLL pollprov.dll provided by Microsoft for SMS 2.0 (I think) and was never fixed in newer versions, at the time I did not know enough about VBscripting to fix the issue and since it was intermittent everybody in the SMS community let it slide (including myself).

I finally figured out another way to get the needed information to make the button work properly so,

I have completely re-written the code for the button so that it no longer uses the faulty DLL.

Users will no logger get the message :

They will now get this message instead:

Note: The button works faster then before if the machine is turned on but it may take a few seconds longer to timeout and give the error message if the machine doesn’t respond.

Note: this same code can be used for SCCM 2007. I will post another blog for that code as well.

Below is a copy of the old code and the new code.

'************************

' Remote Control Button *

'************************

'Old Code

'Sub Btnl_OnClick

' Dim CompName,oWshShell

' CompName = trim(document.frmMain.txtValue.value)

' if Len(Trim(CompName)) = 0 then

' MsgBox "Please type a Machine Name.",,"SMS 2003 Remote Control"

' Else

' Set oWshShell = CreateObject("WScript.Shell")

' 'You will need to edit the following line to fit your environment. SMSServer = Your SMS Server Name

' Set objPing = GetObject("winmgmts://oasms02/root/default:PingPoller")

' 'You will need To edit the following line to fit your environment. SMSServer = Your SMS Server Name

' path = "\\{SMSServerName}\remote$\remote.exe"

' objPing.Trace CompName, "30", "1000", "1", TraceResult, Addresses

' if TraceResult <> 0 then

' MsgBox "Machine did not respond to ping.",,"SMS 2003 Remote Control"

' Else

' 'You will need to edit the following line to fit your environment. SMSServer = Your SMS Server Name

' oWshShell.run path & " 2 " & addresses(ubound(addresses)) & " \\{SMSServerName}\",0,false

' end If

' end If

'End Sub

‘*************************************************************

' New Code written by Chris Stauffer to overcome the ping Failure issue   *

‘*************************************************************

Sub Btnl_OnClick

'You will need to edit the following line to fit your environment. SMSServer = Your SMS Server Name

On Error Resume Next

Dim CompName,oWshShell

CompName = trim(document.frmMain.txtValue.value)

path = "\\{SMSServername}\remote$\remote.exe"

if Len(Trim(CompName)) = 0 then

MsgBox "Please type a Machine Name.",,"SMS 2003 Remote Control"

Else

Set oWshShell = CreateObject("WScript.Shell")

set IPConfigSet = GetObject("winmgmts:{impersonationLevel=impersonate}!//"& CompName &"").ExecQuery("select IPAddress from

Win32_NetworkAdapterConfiguration where IPEnabled=TRUE")

If Err.Number <> 0 Then

MsgBox "Machine Not Found on the network, Please check the name and try again.", 48,"SMS 2003 Remote Control"

Err.Clear

Else

for each IPConfig in IPConfigSet

if Not IsNull(IPConfig.IPAddress) then

for i=LBound(IPConfig.IPAddress) to UBound(IPConfig.IPAddress)

StrIP= IPConfig.IPAddress(i)

'MsgBox "Machine's IPAddress: " & StrIP

Next

End If

next

oWshShell.run path & " 2 " & StrIP & " \\{SMSServerName}\",0,false

End If

end If

End Sub

**************************************************************************************************

(I have a hard time believing i will be attending this year but a man can dream cant he :-)

************************************************************

Early-bird Rates Currently Available

There's no time like the present to come learn how the latest IT management products, solutions and technologies from Microsoft can help reduce costs and maximize availability for your organization.
This year's content will focus on how integrated management solutions can help minimize the cost of planning, deploying and operating IT Services while maximizing their availability within your organization. IT Professionals and Technical Decision Makers—like you—can take advantage of the increased number of Hands-on Labs and breakout sessions at MMS 2009, with extended session and lab hours during the week.

Register today for MMS 2009 and get ready to:

•
Learn about the latest IT management solutions from Microsoft and Partners in more than 120 breakout sessions.

•

Test-drive new products and technologies in the Hands-on Labs, offering over 9,000 lab places, most led by expert instructors!

•

Meet face-to-face with Microsoft and Industry experts, and your peers—in the Expo Hall and at networking events throughout the week.

Learn from the Experts

The sessions at MMS 2009 will again be presented by the top experts in Windows IT Management. Staff from the Microsoft product teams representing the System Center, Windows Server, Windows Client, Security and Solution Accelerator teams will be covering the latest releases, updates and solutions available for IT Management.
In addition, many industry experts and consultants will be presenting the latest best practices and real-world tips and tricks they have developed on customer sites. This includes topics presented by the internal Microsoft IT team, who are typically the first to deploy and manage all Microsoft IT solutions in a live environment.
Finally, you will also be able to hear from your peers – other members of the IT community who have advice, real world lessons and powerful shortcuts to share. Customers actively using Microsoft products to manage their IT environment will be presenting real-world case studies based on their own experiences.

Hands-on Labs

Hands-on Labs, always one of the most popular offerings at MMS each year, return with even more topics in 2009. A wide range of both self-paced and instructor-led lab topics will be provided, allowing attendees to try out a variety of products, solutions and technologies live. Lab topics will cover scenarios such as deployment, upgrade, configuration and administration across a wide range of environments.
This year new lab topics are being added to demonstrate how to integrate multiple products to implement solution scenarios such as "Data Protection and Disaster Recovery" and "End-Point Security Management". In addition new labs topics will explain how to manage a variety of heterogeneous platforms and applications in your environment.

Bring Your Questions to MMS 2009!

Join us at the Venetian Hotel in Las Vegas for a week of deep technical information and tips on how to run your IT infrastructure at maximum efficiency—knowledge you'll get nowhere else!
Learn more about session content, Hands-on Lab topics, and Registration options at http://mms-2009.com/.

I’ve been trying to figure out how to filter out approved and non-approved clients in SCCM. Thanks to David Downs for providing this collection Query information.

Just create a collections and choose system resources then change it to query view and paste in this code.

*****************************************

select SMS_R_SYSTEM.ResourceID

,SMS_R_SYSTEM.ResourceType

,SMS_R_SYSTEM.Name

,SMS_R_SYSTEM.SMSUniqueIdentifier

,SMS_R_SYSTEM.ResourceDomainORWorkgroup

,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_CM_RES_COLL_SMS00001 on SMS_CM_RES_COLL_SMS00001.ResourceId = SMS_R_System.ResourceId

where SMS_CM_RES_COLL_SMS00001.IsApproved= '0'

******************************************

This query can provide 3 different results:

0 = Not Approved

1 = Approved

2 = N/A