I have clamav software installed in my Server (Centos 7) which is under a corporate proxy. I want to stop clamav from trying to download virus databases everytime I try to run freshclam. I'm updating the .cvd files manually every month or so. So how do I stop clamav from downloading frequently.
You should edit file:
/etc/freshclam.conf
find the following line
Checks 24
Then change the number to 0
Checks 0
Or you can stop the cron record for freshclam
Related
When I update a file, like I sent via ftp an update of an existing file, in windows the clients continue to see the previous date and time, I predict to stop and start the smb and nmb service for the clients to see the update. samba-4.10.16-20.el7_9.x86_64 and CentOS Linux release 7.9.2009 (Core), kernel 3.10.0-1160.83.1.el7.x86_64
Update samba and kernel packages
I have been trying to figure out why Wake On Lan works for Right Click Tools, but not for SCCM Scheduled Deployments.
In the wolmgr.log file I found this happening every five seconds: "Failed to get WOL inbox on AMT Proxy component. Wait 5 seconds... SMS_WAKEONLAN_MANAGER 9/19/2018 11:32:24 AM 480 (0x01E0)".
In the wolcmgr.log file I don't see any errors except this happening about four times a day, which I think is referring to the endless errors shown in the other log file: "CBaseCounter::Initialize - Registered performance counter "Total Number of Packets failed" SMS_WAKEONLAN_COMMUNICATION_MANAGER 9/19/2018 2:01:59 AM 9496 (0x2518)"
I have tried to look up these error messages and haven't found anything to help me get this resolved.
I have tried various ports, including the default (9) and 12287, currently it is on 7. We are being told to use subnet directed broadcasts by our network team due to some limitations with our Cisco network configuration.
I do have a SQL Server Agent (ADK) service that was disabled. I enabled it and it starts but turns off immediately. I don't know if that is related at all. I did have some deployment issues with Windows 7 drivers giving errors during the task sequence, even though they were installing. So I installed a Windows 8.1 ADK after seeing an article about bugs with the latest Win10 ADK and SCCM Task Sequences installing Win7 drivers. I've since then installed Win10 1703 ADK, which works on one of my other SCCM servers on Win7 deployments fine, and I was having this WOL problem before installing 1703 ADK.
Under Administration > System Status > Site Status > Management Point, when I show messages I see these:
*Description Severity
Type Site code
Date / Time System
Component Message ID
Thread ID Process ID
The Wake On LAN component has failed to read the site control file settings. Possible cause: The information is not yet available. Solution: The component is waiting for the information to become available and will retry obtaining the information at its next interval. Error
Milestone CML
9/20/2018 12:47:56 PM SMS_WAKEONLAN_MANAGER
6500 3384
3988
Description Severity
Type Site code
Date / Time System
Component Message ID
Thread ID Process ID
The Wake On LAN component has failed to read the site control file settings. Possible cause: The information is not yet available. Solution: The component is waiting for the information to become available and will retry obtaining the information at its next interval. Error
Milestone CML
9/20/2018 9:39:03 AM SMS_WAKEONLAN_MANAGER
6500 2924
2636*
ADK SQL Server Agent
SCCM WOL configuration
WOL ports
wolmgr.log file screen shot
RightClickTools WOL Configuration
My requirement is to restart the windows vm after the software gets installed, I am automating the entire process using chef. Is there any method for doing that?
Can we do through power shell ?
Is there any method for chef to that ?
The windows cookbook offers a reboot resource.
As mentioned above check out the links windows cookbook & windows reboot. All my info is gathered from the previous links.
Include the WindowsRebootHandler in the recipe
include_recipe 'windows::reboot_handler'
Create a reboot block
windows_reboot 30 do
timeout 30
reason 'Restarting computer in 30 seconds!'
action :nothing
end
timeout: timeout delay in seconds before rebooting. default is 60 seconds
reason: reason for the reboot. default is 'Opscode Chef initiated reboot'
Notify the reboot block to trigger the reboot
notifies :request, 'windows_reboot[30]', :delayed
:delayed - notification is queued up and executed at the very end of a chef-client run
:immediately - notification is ran immediately
This morning my Production server (Windows 2008 R2) went offline for 10 mins and also RDP connection was lost for the given duration. During this period the IIS 7 hosted production web site also stopped responding.
Luckily though, after the 10 mins the server was up by its own and RDP session was restored to previous state.
Now the question is how do I find out what went wrong in the server and is there any logs which I can go through verify my findings.
If you goto the run prompt and type eventvwr it will open Event Viewer. From within here expand the Windows Logs tree and look through the System logs. Something will have caused the reboot and you should be able to find it through here.
A good old chesnut is Windows Updates. They aren't on auto install and reboot are they? :]
Is there any way I can see if windows updates installed correctly or failed.
Something like windows update history but through SCCM.
I had some trouble with paths and its ineffective running to the clients and controll.
There are multiple ways to check this, but none of them are really perfect:
use Reporting. e.g. "Management 4 - Deployments that target a computer", "Compliance 4 - Deployment (per update)", ... etc. Or some other report, there are tons of reports that tell you basically the same things.
use logging. You can view the status messages and see if the computer installed updates. But this is more useful for troubleshooting and not for checking if all updates were installed.
the client also writes logfiles into the ccm directory http://technet.microsoft.com/en-us/library/bb693878.aspx
Monitoring > Deployments > Select the deployment > View Status. There, you can see which servers/computers installed, in Progress or Failed the installation. You can also see why they failed such as insufficient disk etc