-
Posts
1,939 -
Joined
-
Last visited
-
Days Won
92
Posts posted by GarthMJ
-
-
17 minutes ago, renoldrobin said:
First off that report doesn't use HW inventory. It use SW inventory. SW inventory is disabled by default as it is useless. https://www.enhansoft.com/sccm-software-inventory/
Instead use the ARP reports to see what is installed on computers.
-
26 minutes ago, paulopires16 said:
GarthMJ, that WSUS is not my area, it's SysAdmin. I see them with a pen drive with update patches that put inside to update all other servers and workstations...
I'm DBA and we need to change SQL Server VM with our instances. For example, one instance for that WSUS with SUSDB database and other instance for SCCM instance with also SUSDB database. I want to optimize that environment. I see 2 SUSDB... Different instances, but why? Why not just one? That's the idea
Thanks
To answer your questions directly about one or two SQL instances for WSUS. Is that it will cause conflicts between the two WSUS Servers if they share a db. Aka if some deploys an software update (SU) on WSUS, it will get installed on CM clients too (outside of CM control). From the CM standpoint, CM will change that products and classifications existing within WSUS, including declining SU too. Thereby stopping any WSU deployment of that SU.
- 1
-
You need to give more details. Pen drive of exactly data what data?
What is the other WSUS server used for, exactly?
-
2 hours ago, paulopires16 said:
Thanks GarthMJ,
The only problem if manage 2 WSUS services on the same domain...
So, for you, what is the best approach? My domain isn't connected to the internet.
- Forget that WSUS Server and install all updates clients from SCCM Server (WSUS inside)?
- Maintain that WSUS Server and add SCCM Server as a client for updates?
- Updates both Server from internet?
Thanks
This is very important details that was missing from your first post.
How exactly are you updating your existing WSUS server now?
Why exactly do you not want to use CM to deploy all SU to all computers? aka why have the second WSUS on the internal network at all?
-
Is the RAID drivers included within WInPE?
-
46 minutes ago, paulopires16 said:
So, GarthMJ what will be the issues if I just install WSUS feature in SCCM Server and then, on WSUS configuration, connect to that same SUSDB database already installed for WSUS server?
This will not be supported and you WILL have problem when you manage WSUS outside of SCCM for non-SCCM computer.
There is NO problem having WSUS installed on the CM server with its own clean db.
- 1
-
1 hour ago, paulopires16 said:
I know how to do it. anyweb I'll check you manuals, thanks
My question remains, what is the best approach? Internal WSUS or uses that WSUS Server?
Thanks
Start with a Clean WSUS server using full SQL server.
- 1
-
you don't want to use an existing WSUS server. You want a fresh one that is use SQL database not WID.
- 1
-
is there a question?
You do know that you don't need a CAS unless you have 150000 computers.
-
It is possible, but your error clearly state that you need to contact MS support to solve this issue. If this for a test lab IMO there is no benefit to having a CAS as it just take up resources on your VM server add headache due to replication issues, etc. Those same resources could be used for other links like, clients or remote WSUS or remote SQL, etc. All of which is better use of resources than a CAS.
-
Unless you have over 150,000 computers you don't need a CAS. If you have more than 150,000 computer then you should be contact MS support for help.
-
That is to be expected if multiple sites are discovering the device. It doesn't hurt anything.
-
WSUS setup hasn't really changed since CM12. So if you are happy with those guides go for it.
-
And did you follow the solution given?
-
Doesn't two deployment work? as mandatory to TCU and second one as available?
-
do you have the SCCM console installed on your computer?
-
I see that you posted this everywhere.
To be honest with you, I would not recommend using SW inventory to do this. Particularly without defining a path for the exe.
Here are several blog on the topic.
https://www.enhansoft.com/sccm-software-inventory/
https://www.enhansoft.com/how-do-you-determine-the-length-of-a-software-inventory-scan-cycle/
https://www.enhansoft.com/slow-software-inventory-cycle-in-sccm-2012/
Just be aware that even if you are scanning just two files. Like I show in this blog. https://www.enhansoft.com/how-do-you-determine-the-length-of-a-software-inventory-scan-cycle/ it can take about an hour or longer to complete.
Heck in this blog it took over 4 hours https://www.enhansoft.com/slow-software-inventory-cycle-in-sccm-2012/ SW inventory now is a low priority process and can take days to complete as just about everythign preempt it. While SW inv is running it will BLOCK both Hardware Inventory and Heartbeat discovery from running.
Honestly if you goal is to uninstall this SW, then I would use a CI to do this as it will happen a lot faster than SW inventory. You can even use the remediation part of a CI to uninstall the SW. You can even use Appblocker to prevent the software for installing/running in the first place too.
-
Have you looked at the AI reports?
-
There is no simple answer each inbox does different things with different log files. The single line that you have posted above does not show a problem, it show that the sender is actually sending data. What you need to determine is the backlog due to slow links or twoo many packages been sent at once or ???
-
You should determine what the problem is and fix that. just cleaning out the files is a bad idea as it hides the problems that you are having.
-
-
This blog will help you determine if the HW inventory has been sent to ther db.
https://www.enhansoft.com/updated-troubleshoot-configmgr-hardware-inventory-issues/
Also force a full inventory. one of these blog will help you with that.
-
Did it update the database?
-
Has Hardware inventory run since it was installed?
How to use software control on SCCM
in System Center Configuration Manager (Current Branch)
Posted
When did you create your SW metering rules? if the has been under 30 days, don't expect anything useful for this report and even then you will really need to wait for 60+ days.