SMS 2003 to SCCM 2007 The Diaries Day II

Dear Friends,

 image

Today I finish a couple of configuration Items on the current Migration of SMS 2003 to SCCM 2007, A very important topic in this migration is Windows Update or ITMU, I leave ITMU Installed on the Server during the Upgrade phase, The installation Upgrade this portion. all Packages of ITMU where migrate correctly into SCCM, Software Update Packages.

On this Case I have to use a Existing WSUS Server.

How to Configure it. go to Site Settings ad Site System right click Select New Server

image

Enter the WSUS Server name on the box and hit Next

 

 image

Select the Software Update Point Role and hit Next

image is

This is optional but use the exact same setting as your wsus server or leave it blank and hit next

image

Use the same ports as the WSUS Server. WARNING If you are configure the WSUS on the same box Remember to put another Port Number to the WSUS as SMS use this for client communication.

image

Use the same settings as your WSUS if you use a upstream server use it if not recommended to sync with Microsoft Updates. and hit next.

 

image

Be my guess make sure you put a schedule that is correct for the company you are doing this configuration, remember your settings may be not the settings the company will use. I recommend use a 12AM Schedule every day. but is my basic configuration.

image

On this section you will have to determine exactly what is compliance for your company or the company you are configuring this. may be the case where the company want all of this settings for this configuration I suggest you only do the basic updates.

 

image

Select all the products you want to do security updates or services packs using the SCCM. I suggest you do all the products you want to do updates for this demo just configure Office and Windows Which is the default for this.

image

in this option if you don’t support international languages don’t select other than English, if you support them remember to select them here also.

image

and you are done you have configure the WSUS to use on the new SCCM.

wait for the synchronization and you will have a full display of the current patches and a summary of the installations.

image

Remember what I just did try to recreate the real configuration on a client using Virtual Lab. I have done this to protect the confidential information of my clients.

If you will like to try some of this labs go to the following link I have provide here and you will see the SMS 2003 to SCCM 2007 Virtual Lab. if you are new to this type of upgrade I suggest you do this lab a couple of times.

Happy upgrade and we continue with the Diaries…

 

SMS 2003 to SCCM 2007 Virtual Lab

SMS 2003 to SCCM 2007 – The Diaries

 


Dear Friends,


 


Have been a Wile since I write a technical stuff on one of my blogs but here is one of the Technical stuff I will write I’m doing a SMS 2003 to SCCM 2007 Migration. The Best ones, well today I was doing the Upgrade as documented by other members of the MVP. but Guess what I get a Error on the configmgrsetup.log I get a error cannot find xp_SMS_notification. and also say this Cannot insert the default site control image to the database.


I dig into a couple of KBs and don’t have any success but then I just put this xp_SMS_Notifications and found this KB is a old KB but looks like the problem still on SCCM 2007, here is the link http://support.microsoft.com/kb/889433


I just want to add to this KB a couple of details.


RESOLUTION


To resolve this problem, you must re-create the xp_SMS_notification extended stored procedure by using SQL Enterprise Manager. To do this, follow these steps:

1.
Click Start, point to Programs, point to Microsoft SQL Server, and then click SQL Management Studio.

2.
In SQL Enterprise Manager, expand Microsoft SQL Servers, expand SQL Server Group, expand ServerName, expand Databases, and then click master.

3.
In the right pane of SQL Management Studio, right-click Extended Stored Procedure, and then click New Extended Stored Procedure.

4.
In the Extended Stored Procedure Properties – ServerName dialog box, type xp_SMS_notification, and then click the ellipses (…) button next to Path.
Important The Extended Stored Procedure name is case-sensitive and must be entered as xp_SMS_notification.

5.
In the Locate Extended Stored Procedure .DLL dialog box, locate the \SMS\Bin\i386 folder, click smsxp.dll, and then click OK two times.

6. Then go to permissions of the Stored Procedures and Give permissions to the SMS Admins Group and NT AUTHORITY\System

7. Re run the SCCM 2007 Upgrade

I will try to create a Community KB and then upload it. but here is what I have so far if you guys have the same problem let me know. reply here or post.


http://support.microsoft.com/kb/556084/en-us


 

TechEd 2008 In-Between

Dear Friends,

 

 

Do you love Tech Ed,

 

What about having a pre-event for free, you got it IT Pro Camp Orlando Convention Center June 7 and June 8 2008. All thinks you love about IT Pro Event, Tech Net Events, all for free this date on the Orlando Convention Center.

 

Please Register today using www.itprocamp.com

 

This is the First Florida IT Pro Camp. If you are visiting the TechEd, go these dates, if you cannot go to the TechEd well come to the IT Pro Camp is for Free and you will never regret.

 

We you you guys register and keep the eye the next IT Pro Camp can be in your hometown.

 

Santos Martinez

Windows Server System – SQL Server MVP

Mentor

Call for Speakers at IT Pro Camp

Dear IT Pro’s,
 
 We are planning our First big Orlando IT Pro Camp Event, In order to cordinate the following event we are looking for Speakers on the IT Pro Area, if you are interested please fill the following form, This event will be free so feel free to invite all people you may know are interested on Speaking or attend, please foward this invitation to all the people you know and help us get all the speakers we need.


 


more details about the event here at http://www.itprocamp.com


 

System Center Configuration Manager Beta Exam

 

Invitation

You are invited to take beta exam 70-401: TS: Microsoft System Center Configuration Manager 2007, Configuring. If you pass the beta exam, the exam credit will be added to your transcript and you will not need to take the exam in its released form.

By participating in beta exams, you have the opportunity to provide the Microsoft Certification program with feedback about exam content, which is integral to development of exams in their released version. We depend on the contributions of experienced IT professionals and developers as we continually improve exam content and maintain the value of Microsoft certifications.

71401: TS: Microsoft System Center Configuration Manager 2007, Configuring counts as credit towards the following certification(s).

•  Microsoft Certified Technology Specialist (MCTS): System Center Configuration Manager 2007, Configuration


Availability

  • Registration begins: November 21, 2007
  • Beta exam period runs: November 28, 2007– December 18, 2007
  • Receiving this invitation does not guarantee you a seat in the beta; we recommend that you register immediately. Beta exams have limited availability and are operated under a first-come-first-served basis. Once all beta slots are filled, no additional seats will be offered.
  • Testing is held at Prometric testing centers worldwide, although this exam may not be available in all countries (see Regional Restrictions). All testing centers will have the capability to offer this exam in its live version.
  • Regional Restrictions: India, Pakistan, China

Registration Information

  • You must register at least 24 hours prior to taking the exam.
  • Please use the following promotional code when registering for the exam: B401
  • Receiving this invitation does not guarantee you a seat in the beta; we recommend that you register immediately.

To register in North America, please call:

•  Prometric: (800) 755-EXAM (800-755-3926)

Outside the U.S./Canada, please contact:

•  Prometric: http://www.register.prometric.com/ClientInformation.asp


Test Information and Support

You are invited to take this beta exam at no charge.
You will be given four hours to complete the beta exam. Please plan accordingly.
Find exam preparation information:
http://www.microsoft.com/learning/exams/70-401.mspx

The Mystery of the Lost Hardware Inventory by Ross Slaten

Dear Friends,

Another very good friend send me this article to fix a problem that we have and i think will be interesting to the communities if i post this on my blogs so many people read it. the original article link is http://blogs.msdn.com/rslaten/archive/2007/09/18/the-mystery-of-the-lost-hardware-inventory.aspx

 

and here is the details of it.

The Mystery of the Lost Hardware Inventory

In large environments, with tens of thousands of SMS 2003 clients, inventory may get “lost” for various reasons. An example of a lost inventory is below:

  • An SMS 2003 Advanced Client reports a full inventory upon install
  • The client continues to report delta inventory of changes
  • The client reports a delta inventory but that inventory gets “lost”
  • The client continues to report delta inventory but the changes in the “lost” inventory never appear in the database
  • The client gets resync’d, sending up a full inventory, and the changes that were “lost” now appear

Clients don’t get resync’d under normal conditions therefore that inventory may not ever appear in the database. This can become an issue for inventory items such as security updates (staying applicable in the database but not applicable on the client). System Center Configuration Manager 2007 contains architectural changes which prevent this scenario from occurring. Specifically SCCM 2007 serializes software and hardware inventory reporting so that missing reports, which are based on serial numbers instead of timestamps, trigger a re-synchronization of inventory at the client.
So if you don’t plan on upgrading to SCCM 2007 in the near future how might you prevent inventory from being “lost”? I documented some steps that should assist with detecting, and possibly resolving, the rare scenario when clients send up inventory that somehow disappears before getting loaded into the database. These steps are simply an example of how one might do this and the scripts are not tested and do not contain any type of error handling, logging, or reporting.
Step # 1 – Modify the SMS_DEF.MOF

  • Modify the Win32_OperatingSystem section of the MOF to report “LocalDateTime”.  This is required because the “Workstation Status” section shows “Last Hardware Scan” but there isn’t a way to keep the history of this data therefore we need a consistent time we can key in on that writes to a history table.
  • Create a new class in the SMS_DEF.MOF to pick up a new WMI class which we’ll create a populate later:

    //SMSInventoryHistory
     [SMS_Report(TRUE),
    SMS_Group_Name(“SMS Inventory”),
    SMS_Class_ID(“MICROSOFT|SMS_INVENTORY|1.0”),
    Namespace(“\\\\\\\\.\\\\root\\\\SMSINVENTORY“)]
    class InvHistory: SMS_Class_Template
    {
    [SMS_Report(TRUE),key]
    datetime   ScanTime;
    [SMS_Report(TRUE)]
    uint32   KeyIncrement;
    [SMS_Report(TRUE)]
    string   ScanType;
    };

  • Notice the KeyIncrement field.  This is there because we want to report every instance of this class for every inventory.  It is for this reason that we don’t need history enabled for this class so it can be disabled by using KB836432 (This still applies to SMS 2003 and likely SCCM 2007).

Step # 2 – Create a recurring advertisement, which should probably run at least twice as often as hardware inventory (if not more), which runs client.vbs

  • Creates a new “SMSInventory” class under “root” if it doesn’t exist
  • Gets the last hardware scan from root\ccm\invagt:InventoryActionStatus
  • Creates a new instance of InvHistory in the SMSInventory namespace if the hardware scan is new
  • If the inventory is already recorded then update the “KeyIncrement” field so SMS reports this in every delta
  • Cleans up any instances older than 14 days by default to keep the delta inventory from growing too large
'client.vbs
'rslaten
'08/15/2007

'Determines when to clean out old inventory instances
iDays = 14

'Connect to WMI locally
Set oLocator = CreateObject("WbemScripting.sWbemLocator")
Set oSvc = oLocator.ConnectServer(".", "root")

'Create a custom namespace to hold data if it doesn't already exist
Set oNamespaces = oSvc.InstancesOf("__namespace")
bFound = False
For each oNamespace in oNamespaces
    If oNamespace.Name = "SMSInventory" Then
        bFound = True
        Exit For
    End If
Next

If Not bFound Then
    Set oNamespace = oSvc.Get("__namespace")
    Set oCustomNameSpace = oNamespace.SpawnInstance_
    oCustomNamespace.name = "SMSInventory"
    oCustomNamespace.Put_()

    'Create a custom class to hold data
    wbemCimtypeUint32 = 19
    wbemCimtypeDatetime = 101
    wbemCimtypeString = 8
    Set oWMI = GetObject("winmgmts:root\SMSInventory")
    Set oClass = oWMI.Get()
    oClass.Path_.Class = "InvHistory"
    oClass.Properties_.add "ScanTime", wbemCimtypeDatetime
    oClass.Properties_("ScanTime").Qualifiers_.add "key", true
    oClass.Properties_.add "KeyIncrement", wbemCimtypeUint32
    oClass.Properties_.add "ScanType", wbemCimtypeString
    oClass.Put_()
End If

'Get timezone
Set oSvc = oLocator.ConnectServer(".", "root\cimv2")
Set collTimeZone = oSvc.ExecQuery("select Bias, DaylightBias from Win32_TimeZone")
For Each oTimeZone in collTimeZone
    iTimeZone = oTimeZone.Bias - oTimeZone.DaylightBias
Next

'Get last Hinv report date and convert to local time
Set oSvc = oLocator.ConnectServer(".", "root\ccm\invagt")
HActionID = """{00000000-0000-0000-0000-000000000001}"""
Set oHinv = oSvc.Get("InventoryActionStatus.InventoryActionID=" & _
    HActionID)
Const CONVERT_TO_LOCAL_TIME = true
'dLastReportDate = ConvertToGMT(oHinv.LastReportDate)
dLastReportDate = oHinv.LastReportDate
dLastReportDate = WMIDateStringToDate(dLastReportDate)
Set dNewTime = CreateObject("WbemScripting.SWbemDateTime")
dNewTime.SetVarDate dLastReportDate, CONVERT_TO_LOCAL_TIME
dLastReportDate = dNewTime.GetVarDate(CONVERT_TO_LOCAL_TIME)
dLastReportDate = DateAdd("n", iTimeZone, dLastReportDate)
dLastReportDate = GetWMIDate(dLastReportDate, "+000")

'Set last Hinv report date
Set oSvc = oLocator.ConnectServer(".", "root\SMSInventory")
Set oHinvHistory = oSvc.InstancesOf("InvHistory")

'First instance in class
If oHinvHistory.Count = 0 Then
    Set oHinv = oSvc.Get("InvHistory").SpawnInstance_
    oHinv.ScanTime = dLastReportDate
    oHinv.KeyIncrement = 0
    oHinv.ScanType = "Hardware"
    oHinv.Put_()
Else
    bFound = False
    
    'Calculate date to clean up old instances
    Set dExpire = CreateObject("WbemScripting.SWbemDateTime")
    dExpire.SetVarDate Now, CONVERT_TO_LOCAL_TIME
    dRegular = dExpire.GetVarDate(CONVERT_TO_LOCAL_TIME)
    dExpireDate = DateAdd("d", -iDays, dRegular)
    dExpire.SetVarDate dExpireDate, CONVERT_TO_LOCAL_TIME
    
    'Updating all instances
    For each oInstance in oHinvHistory
        If dLastReportDate = oInstance.ScanTime Then
            bFound = True
        End If
        
        'Clean up old instances
        If oInstance.ScanTime < dExpire Then
            oInstance.Delete_
        Else
            'Increment the KeyIncrement property to force SMS to pick
            'up the instance during inventory
            oInstance.KeyIncrement = oInstance.KeyIncrement + 1
            oInstance.Put_
        End If
    Next
    
    'Create a new instance if needed
    If Not bFound Then
        Set oHinv = oSvc.Get("InvHistory").SpawnInstance_
        oHinv.ScanTime = dLastReportDate
        oHinv.KeyIncrement = 0
        oHinv.ScanType = "Hardware"
        oHinv.Put_()    
    End If
End If

Function ConvertToGMT(dDate)
    ConvertToGMT = Replace(dDate, "-000", iTimeZone)
End Function

Function WMIDateStringToDate(dtmInstallDate)
     WMIDateStringToDate = CDate(Mid(dtmInstallDate, 5, 2) & "/" & _
     Mid(dtmInstallDate, 7, 2) & "/" & Left(dtmInstallDate, 4) _
     & " " & Mid (dtmInstallDate, 9, 2) & ":" & _
     Mid(dtmInstallDate, 11, 2) & ":" & Mid(dtmInstallDate, _
     13, 2))
End Function

Function GetWMIDate(vd,strOffset)
    On Error Resume Next
    GetWMIDate = Year(vd) & AddZero(Month(vd)) & AddZero(Day(vd)) & _
            AddZero(Hour(vd)) & AddZero(Minute(vd)) & _
            AddZero(Second(vd)) & ".000000" & strOffset
End Function

Function AddZero(pNum)
    On Error Resume Next
    If pNum <=9 then
        AddZero = "0" & pNum
    Else AddZero = pNum
    End If
End Function

.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }

Step # 3 – Periodically check to see if there is any missing hardware inventory by running server.vbs

  • Queries the SMS database for OS LocalDateTime and the custom SMSInventory ScanTime
  • Compares the ScanTime to LocalDateTime, searching for missing LocalDateTime entries.  To find a match the LocalDateTime must be within 5 minutes from the ScanTime.  If any clients take longer than 5 minutes to complete a hardware inventory cycle then this may need to be increased.
  • For any ScanTime without a matching LocalDateTime, we display the fact that there is a missing inventory.
'server.vbs
'rslaten
'08/15/2007

'Globals
Dim aClients(), iClients, iInstanceCount, iTotal

'Get SMS Namespace
sSMSNameSpace = GetSMSNameSpace()

'Connect to site server
Set oWMI = GetObject("winMgmts:" & sSMSNameSpace)

'Query clients and create and array of client objects
sQuery = "select distinct SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier," & _
    " SMS_G_System_SMS_INVENTORY.ScanTime, SMS_GH_System_OPERATING_SYSTEM.LocalDateTime" & _
    " from  SMS_R_System inner join SMS_G_System_SMS_INVENTORY on " & _
    "SMS_G_System_SMS_INVENTORY.ResourceID = SMS_R_System.ResourceId inner" & _
    " join SMS_GH_System_OPERATING_SYSTEM on " & _
    "SMS_GH_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId " & _
    "where SMS_G_System_SMS_INVENTORY.ScanTime is not NULL and " & _
    "SMS_GH_System_OPERATING_SYSTEM.LocalDateTime is not NULL"

Set aCollection = oWMI.ExecQuery(sQuery)
iTotal = aCollection.count
For Each oInstance In aCollection
    If sLastName <> oInstance.SMS_R_System.Name Then
        'Make sure this isn't the first iteration in the array
        If iInstanceCount <> 0 Then
            'Add to master array
            ReDim Preserve aClients(iClients)
            Set aClients(iClients) = oClient
            iClients = iClients + 1
        End If
        
        'Now create new client object
        Set oClient = New Client
        oClient.sClient = oInstance.SMS_R_System.Name
        oClient.sGUID = oInstance.SMS_R_System.SMSUniqueIdentifier
    End If
    
    If sLastScan <> oInstance.SMS_G_System_SMS_Inventory.ScanTime Then
        oClient.AddSMSInventoryScanDate(oInstance.SMS_G_System_SMS_Inventory.ScanTime)
    End If
    
    If sLastOSScan <> oInstance.SMS_GH_System_OPERATING_SYSTEM.LocalDateTime Then
        oClient.AddOSScanDate(oInstance.SMS_GH_System_OPERATING_SYSTEM.LocalDateTime)
    End If 

    sLastName = oInstance.SMS_R_System.Name
    sLastScan = oInstance.SMS_G_System_SMS_Inventory.ScanTime
    sLastOSScan = oInstance.SMS_GH_System_OPERATING_SYSTEM.LocalDateTime
    iInstanceCount = iInstanceCount + 1
    
    'If this is the last instance add it to the array
    If iInstanceCount = iTotal Then
        'Add to master array
        ReDim Preserve aClients(iClients)
        Set aClients(iClients) = oClient
        iClients = iClients + 1    
    End If
Next

'Loop through clients in memory to check for missing inventory
For each oClient in aClients
    aScans = oClient.aScans
    WScript.Echo "******************************************"
    WScript.Echo "Client = " & oClient.sClient
    WScript.Echo "GUID = " & oClient.sGUID
    For each oScan in oClient.aScans
        If not oScan.isOS Then
            Set oMatch = new Match
            oMatch.dScan = WMIDateStringToDate(oScan.dDate)
            oMatch.bMatch = false
            
            'Find a matching OS time (look for match within 5 minutes)
            For each oTime in aScans
                If oTime.isOS Then
                    If DateDiff("n", oMatch.dScan, _
                        WMIDateStringToDate(oTime.dDate)) < 5 and _
                        DateDiff ("n", oMatch.dScan, _
                        WMIDateStringToDate(oTime.dDate)) > -5 Then             
                        oMatch.dOS = WMIDateStringToDate(oTime.dDate)
                        oMatch.bMatch = true
                    End If
                End If
            Next
            
            'Make sure we found a match
            If not oMatch.bMatch Then
                WScript.Echo "*PROBLEM FOUND*"
                WScript.Echo "SMS Inventory Report = " & oMatch.dScan
                WScript.Echo "*NO MATCHING OS DATE FOUND*"
            Else
                WScript.Echo oMatch.dScan & " = " & oMatch.dOS
            End If
        End If
    Next
    WScript.Echo "******************************************"
Next

'Get regular date
Function WMIDateStringToDate(dtmInstallDate)
    WMIDateStringToDate = CDate(Mid(dtmInstallDate, 5, 2) & "/" & _
        Mid(dtmInstallDate, 7, 2) & "/" & Left(dtmInstallDate, 4) _
            & " " & Mid (dtmInstallDate, 9, 2) & ":" & _
                Mid(dtmInstallDate, 11, 2) & ":" & Mid(dtmInstallDate, _
                    13, 2))
End Function


'Gets SMS Namespace from local site server
Function GetSMSNameSpace()
    Set refWMI = GetObject("winMgmts:\root\sms")    
    Set colNameSpaceQuery = refWMI.ExecQuery("select * from SMS_ProviderLocation")
    For Each refitem in colNameSpaceQuery
        GetSMSNameSpace = refitem.NamespacePath
    Next
End Function

Class Client
    Public aScans()
    Private i
    Public sClient
    Public sGUID
    
    Public Sub AddOSScanDate(dScanDate)
        'Check for duplicates
        bFound = false
        For Each oScan in aScans
            If dScanDate = oScan.dDate And _
                oScan.isOS = true Then
                bFound = true
                Exit For
            End If
        Next
        
        If Not bFound Then
            Set oScan = New Scan
            oScan.dDate = dScanDate
            oScan.isOS = true
            ReDim Preserve aScans(i)
            Set aScans(i) = oScan
            i = i + 1
        End If
    End Sub
    
    Public Sub AddSMSInventoryScanDate(dScanDate)
        'Check for duplicates
        bFound = false
        For Each oScan in aScans
            If dScanDate = oScan.dDate And _
                oScan.isOS = false Then
                bFound = true
                Exit For
            End If
        Next
        
        If Not bFound Then        
            Set oScan = New Scan
            oScan.dDate = dScanDate
            oScan.isOS = false
            ReDim Preserve aScans(i)
            Set aScans(i) = oScan
            i = i + 1    
        End If
    End Sub
End Class

Class Scan
    Public dDate
    Public isOS
End Class

Class Match
    Public dScan
    Public dOS
    Public bMatch
End Class

.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }

Step # 4 – Force a resync on the clients that have “lost” inventory

  • The method to delete the local inventory cache is the known and documented method of doing this.
  • There may be a way to use the MP API to create a server side policy, but this would require significant work and a non-script (C++) application.  Internally, as you can see with SQL profiler, we execute the sp_RC_InvResync stored procedure but as you know executing these directly isn’t recommended or supported.

These examples do not contain error checking and need to be optimized for performance.  The examples have also only been tested in a very small test environment using only the scenario documented at the top of this post.  If this method is to be used in a production environment more code work and testing needs to be done, particularly on the server end, to improve the detection logic, add history to which clients resyncs have been sent to, and add reporting capabilities.

**Steps 3 and 4 might not be required.  During testing I found a potentially unforeseen benefit of running the client.vbs script on clients with “lost” inventory.  Since every instance of the InvHistory class is reported during every inventory, when an instance is listed as “Update” but isn’t in the database, dataloader will automatically request a resync for that client.  More testing of this finding needs to be done to verify that this will work, and if it does it should simplify detecting which clients have lost inventory**

I hope you like it guys.

Santos Martinez

Windows Server System – SQL Server MVP

Windows Vista SP1 Beta

Dear All,

 

A Couple of weeks ago I receive the invite to be part of the Windows Vista SP1 Beta, if you guys are interested on be part of Microsoft Beta Products you can do it true http://connect.microsoft.com and get the betas you want to share my experience installing the beta using WU Technology. this have been a nice update how ever still on beta folks if have time to apply for connect and be part of all the betas they offer I recommended that you guys do it there are a lot of betas like SCCM for those interested on testing it.

 

Santos Martinez, MCSE Security

smartinezpr@gmail.com

http://www.itsecdata.net

SarasotaITPro

Have been a wile since my last post now I’m posting that we will made a call to all Sarasota, Florida IT Pros to join us into our staff call to get started with the community this community will be sponsored by ITSecData, Inc and Microsoft

please send me a email to smartinezpr@gmail.com

 

all members will have email address from sarasotaitpro.org.