Re: Problem- Bad link in SCCM 2007 R2 documentation

I'm not sure what your second problem is, What is the issue you are having?

Here is a link to the docs:

ConfigMgr
http://technet.microsoft.com/en-us/library/bb680651.aspx

SMS 2k3
http://technet.microsoft.com/en-us/library/cc181833.aspx


BTW ConfigMgr is not 64bit so are are fine that way.


"Beoweolf" <zenner@xxxxxxxxxxxxxxx> wrote in message news:5B594D09-9F84-47FB-ACF9-BE380E0FED03@xxxxxxxxxxxxxxxx
I have inherited an SMS 2003 setup. My problems are at least 2. First, our clients have all moved to Vista, This installation of SMS will not recognize them. I installed the recommended updates to bring it to R2 level, which I believed were the solution to the Vista recognition problem.

My domain is 2003 forest and domain level, the DC holding FSMO roles is server 2003, although I have installed both a member server and another DC with Server 2008 OS's.

I could move to SCCM, but that brings in an addition learning curve, software costs and equipment and change over to 64 bit set of problems that I am not ready to suffer through, yet.

Any suggestions on documentation or OJT experiences that can help me through these problems?

"Todd Miller" <ToddMiller@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:27E636DE-D700-4B01-8105-8AF1EFD94132@xxxxxxxxxxxxxxxx
The web page that describes how to install the Application Virtualization
client for use with SCCM
http://technet.microsoft.com/en-us/library/cc512024.aspx
has a link to "Microsoft Application Error Reporting" information, but this
link instead points to a Plugin for IE 8 beta. I was unable to find any
articles that describe how to install Microsoft Application Error Reporting,
but it is probably worth mentioning that the MSI for this component is
located in the App-V download. When you decompress the App-V Zip file
DW20SHARED.MSI can be found at CLIENT\SUPPORT\WATSON. Someone on the SCCM
2007 documentation team should get this fixed up.


.

Relevant Pages

  • Re: After reinstallation
    ... If you manually install the client and open the system manager in control ... See Ccm.log on site server ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... The MP installation was succesful, ...
    (microsoft.public.sms.setup)
  • Re: Client not reporting into SCCM
    ... We are not trying to get any SMS 2k3 client reporting into SCCM. ... the schema not extended to SCCM and a designated SITE Code. ... SCCM Server on a seperate server SQL ...
    (microsoft.public.sms.misc)
  • Re:W2k Terminal Service work abnormally after install SMS 2003 Advanced Client?
    ... After you install the Microsoft Systems Management Server (SMS) 2003 ... Advanced Client software, it may take several minutes to log off a Terminal ... Also follow the installation ...
    (microsoft.public.sms.admin)
  • Re: Repointing Primary Site to New Database Server
    ... Do I re-enable the SCCM services then perform a site reset through SCCM ConfigMgr as the Console just hangs when accessing it. ... The SQL2k5 database server I was originally using keeps failing so I have installed SQL 2K5 on the Primary Site server and would now like to know how to point the Primary site to the new server and DB. ... You cannot move the sms provider back to the sms server it was installed on a remote machine previously in sms 2003. ... Windows Server System MVP - SMS ...
    (microsoft.public.sms.setup)
  • Re: Non AD client push problems
    ... Look at the ccm.log and smsprov.log on the site server to see if ccr's are ... > SMS 2003 with SP1 on a separate server. ... We have approximately 400 workstations (XP Client ... Under the client push installation we are using are SMSService ...
    (microsoft.public.sms.setup)
Loading