the part he was looking at comes from discovery and heartbeat

prolly has a dormant client or duplicate record

On Wed, Jul 31, 2013 at 8:08 AM, Jason Sandys <[email protected]> wrote:

>  He meant that the system being inventoried was a refresh not ConfigMgr
> as a whole – that’s why he asked if you had tried deleting the resource.**
> **
>
> ** **
>
> J****
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *JRIT
> *Sent:* Tuesday, July 30, 2013 7:31 PM
> *To:* [email protected]
> *Subject:* Re: [mssms] Operating System Name****
>
> ** **
>
> No, its a fresh SCCM installation... ****
>
> ** **
>
> 2013/7/30 Johns, Damon (DoJ) <[email protected]>****
>
>  Did you refresh that computer from Vista to Windows 7? I have seen
> sometimes were the Operating System version is not recorded correctly in
> the CM DB when doing a refresh.****
>
>  ****
>
> Delete the client out of your CM and allow it to be re-created. Should
> resolve the problem.****
>
>  ****
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *JRIT
> *Sent:* Wednesday, 31 July 2013 4:28 AM
> *To:* [email protected]
> *Subject:* [mssms] Operating System Name****
>
>  ****
>
> Please folks, can you help me with two questions?****
>
>
> 01. Where ConfigMgr find Operating System Name and Version property? It is
> not present in Computer object inside Active Directory.
>
> 02. I have one Windows 7 showing as Windows NT Workstation 6.0. But 6.0 is
> Windows Vista, Windows 7 is 6.1, why this is happening? All my other
> Windows 7 is showing 6.1 version, juts that is 6.0, see print below:
>
>
> [image: Imagem inline 2]****
>
>  ****
>
> ** **
>  ------------------------------
>
>
> CONFIDENTIALITY NOTICE AND DISCLAIMER
> The information in this transmission may be confidential and/or protected
> by legal professional privilege, and is intended only for the person or
> persons to whom it is addressed. If you are not such a person, you are
> warned that any disclosure, copying or dissemination of the information is
> unauthorised. If you have received the transmission in error, please
> immediately contact this office by telephone, fax or email, to inform us of
> the error and to enable arrangements to be made for the destruction of the
> transmission, or its return at our cost. No liability is accepted for any
> unauthorised use of the information contained in this transmission.****
>
> ** **
>
>  ** **
>
> ** **
>
>



<<image001.jpg>>

Reply via email to