-
Posts
1,939 -
Joined
-
Last visited
-
Days Won
92
Posts posted by GarthMJ
-
-
16 minutes ago, Matt Kemp said:
Hi All,
Sorry if this is has already been discussed,
I look after a global SCCM Environment, 1 CAS Server, 2 Primary Sites and 40+ Distribution Points.
OSD:
Some of our clients in the US are unable to retrieve policy due to a Time Sync with the primary site.
SMSTS.log on an affected client states the following:
Failed to get Client Identity (80072ee2)
SyncTimeWithMP() failed 80072ee2
Failed to get time information from MP: http:\\xxxxxxxxxxxx
The US Primary Site is set to UTC Eastern Time -05:00. Clients with timezone UTC Pacific Time -08:00 seem to be affected.
How can i support both timezones?
Thanks
Matt
80072ee2 = timeout
This is almost always a firewall / network issues.
-
1 hour ago, bmkiss67 said:
My thing with the SCCM interface is that customers like pretty things so when they want to see patch data they want to see it in the SCCM interface.
I would disagree with you. Do you really want to give your management the SCCM console, just to look at reports? No, they would generally want them emailed to them. Reports can be pretty too, you need to take time to make them or find either (free or paid) reports.
Don't forget that you will need to update those consoles ever 3-4 months when you update to the latest version of CMCB, this is not a great experience for them.
-
Yes but it will always be out of date, so why not use the reports?
-
This is to be expected, Reporting is always 100% correct, whereas the console uses cached results.
-
When you created the SSRS SQL Server instance, did you create it with that name or did you create it with "SSRS", from the screenshot above it look like the later.
-
2 minutes ago, jnfarmer said:
Where would I find that?
I'm not sure what you mean by this. What exactly are you trying to find? i'm not seeing anything wrong with this setup.
-
What is displayed is the instance name not the database name. This mean you setup your instance as SSRS
-
Glad everything is working for you now.
-
That is because CM's SQL requires 8 GB of RAM for itself as a bare min. You will never get CM up with just 4 GB of ram, you will need at least 10GB
- 1
-
I'm guessing but so did you set the system account account to English too? Is the OS English or German?
-
I believe that this is based on the SSRS server language, once that is changed you might need to re-install your reporting point.
-
1 hour ago, Bhavay said:
I am facing the same issue, package is getting distributed on all DPs, expect for one where it fails with same error. was anyone able to find a solution to it? Any help will be appreciated.
did you check to see if the file exist at the location in question?
-
No, not without customizing the report and even then Version is not a number it is a string. So you get odd results.
-
Have you looked at the builtin reporting for SCCM?
-
When you look on your CAS, do you see the devices?
I hope you didn't use the same site code for the new server.
-
How do you know AD discovery is finding devices? Is the DNS entry correct? Where are you looking at the collection on your CAS? Is your replication healthy?
-
You should always use v_r_System_Valid. Otherwise you could bu looking at deleted computers too. Take a look at this blog, it also applies to CMCB too.
-
you need to use the count command.
SELECT
RV.Netbios_Name0 as 'Computer',
Count(UP.localPath0) as '# of Profiles'
FROM
dbo.v_R_System_Valid RV
INNER JOIN dbo.v_GS_USER_PROFILE UP ON UP.ResourceID = RV.ResourceID
WHERE
UP.localPath0 IS NOT NULL
GROUP BY
RV.Netbios_Name0
ORDER BY
RV.Netbios_Name0 -
First off in AI I would turn ON USB and turn OFF Shortcuts, in any case these have nothing to do with SW inventory.
Second, I would review the InventoryAgent.log on any computer to confirm that SW inventory is working. look for the text {00000000-0000-0000-0000-000000000002}. Personally, I would turn off SW inventory altogether as it is useless.
-
It is document in the CM docs that your site server must be SA within SQL/SSRS. So I don't see this as a problem or issue.
Again, it is unclear if you have actually configured SW inventory. Post a screenshot.
Again, it is not recommended that SW inv be used and there is no guarantee that it will return results, lots to read here https://www.enhansoft.com/?s=software+inventory
-
It will not be a permissions issue for SW inv., why because if HW inventory is working then SW inv will work too.
So this thread started with SSRS problem and has move the SW inv. so is the SSRS problem fixed? for SW inv, have you confirmed that it is actually being inventoried on a client computer?
-
If you just configured it, now you have to wait several days for results to show up. However again, keep in mind that I NEVER recommend doing a *.exe. some light reading. https://www.enhansoft.com/?s=software+inventory
-
Did you configure SW inv? if so exactly what did you configure? aka why do you think it is unhealthy?
-
You can get the version number from ARP reports too.
SW Inv is NOT configured when you first setup CMCB. until it is configured, it will never return anything. aka blank reports.
SCCM Design question
in System Center Configuration Manager (Current Branch)
Posted
Secondly site don't work like that you must have access to the primary site server.