So you've confirmed it's not permissions on AD (the machine account for your
ConfigMGr server can see/read the OU /OUs you are querying?) That was going
to be my next suggestion.
--
Standarize. Simplify. Automate.
"Russ B" wrote:
I just did install that patch, but would that cause discovery not to work. I
did check the adsysdis.log file and it appears as if the system is seeing
devices, but not updating collections.
I have a new SCCM 2007 installation. I installed it in Native Mode following
the PKI instructions. My network is setup as follows.
2 DC's both GC's 1 Forest, 1 Domain
76 Windows Servers
1300 Windows PCs (2000 SP4 and higher)
My issue is this, after SCCM was installed, I verified that the Schema was
extended and updated correctly, there are no errors in the event logs or the
SCCM logs (that I can discern), but I cannot get the discovery to take place.
I have entered my border as the default-first-site-name and my discovery is
Active directory Systems using the local domain. I have no clue why I can
only see the SCCM server in the collections. Can someone give me some
direction here?
Re: Failed upgrade to SCCM ... need to completely uninstall SCCM components, then perform a full installation of SCCM on the server with the same name and site code and then do a "site repair" using the backup of our existing SCCM database. ... I recently started the upgrade our SMS 2003 SP3 Server to SCCM. ... The prerequisite checker passed for everything except inactive clients and SQL Server security mode and as we require the SQL server to be in SQL & Windows Authentication mode we cannot change this. ... I started the installation and everything seemed to be going well until the very end where everything completed successfully except "Install management point" and "Install site control manager" with status "Unknown" I pressed finish and attempted to open the ConfigMgr Console however it hung on loading. ... (microsoft.public.sms.setup)
Re: Client not reporting into SCCM ... We are currently running our own SCCM SP1 (stating the SITECODE=TST, ... different division that has full control of the forest and schema....SCCM Server on a seperate server SQL ... of life so we built a new server loaded SCCM SP1 with R2 and client are ... (microsoft.public.sms.misc)
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: Client not reporting into SCCM ... Do anything from SCCM associated with the server IP or just the netbios name? ... Hence why it is easier to create a new site with new site code and force over the clients to the new site. ... We are treated as a seperate entity, but still a member of the forest (that is why we can't extend the schema), we currently running a working SCCM SP1 without the schema extended with are workstations containing the SCCM client. ... (microsoft.public.sms.misc)
Re: Client not reporting into SCCM ... an SMS/Configmgr site code cannot be more than 3 characters. ... but I can't think of how that relates to a side-by-side upgrade.... Do anything from SCCM associated with the server... we currently running a working SCCM SP1... (microsoft.public.sms.misc)
