SAMBA - Updated file does not reflect to windows clients - centos

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

Related

How can I copy script from Rundeck server to a brand-new Windows Server

One of the requirements is to keep remote Windows Server intact.
No third party software allowed (no WinSCP, etc).
So we configure Windows Server with WinRM and allow remote access, AllowUnencrypted=true, Auth basic=true, etc...
Then we create job and execute command on Windows server like "ifconfig" successfully.
When it comes to executing inline script or copying file - Rundeck is trying to copy script/file to remote Windows server.
By default:
plugin.script-copy.default.command=get-services
where "get-services" seems to be free-form text rather than executable.
If we want to use SCP or SSH instead, here we have problem -> Windows Server doesn't have WinSCP or SSH or Python installed by default.
Is there any way to copy/deliver script to target/remote Windows Server 2008 using embedded capabilities only (no third-party software allowed) ?
Versions:
Rundeck 2.6.2 running on Linux
Windows Server 2008 R2 Enterprise, Service Pack 1
Thank you.
You can use the WinRM plugin (AKA "Overthere WinRM"), configure it, and use the copy file step on your job workflow (keep in mind that you need the 1.3.4 WinRM plugin at least which support copy file).
You need to download the plugin and put it in Rundeck the libext directory.
Add the Windows resources.xml entry (for "Overthere" WinRM plugin):
<node name="windows" description="Windows node" tags="" hostname="192.168.1.81" osArch="x86" osFamily="windows" osName="Windows 2008R2" osVersion="2008" username="user" winrm-protocol="http" winrm-auth-type="basic" winrm-cmd="CMD" winrm-password-storage-path="keys/winpasswd"/>
Set WinRM as your default node executor / default node file copier, and use the copy file step on your workflow like this.
So, this is important: the WinRM plugin isn't in active development (and Rundeck 2.6 branch is out of support/maintenance), the best way to deal with this is to move to the latest Rundeck version and use the PyWinRM plugin (out of the box with Rundeck, on active development and easiest to configure compared by the old "Overthere" WinRM plugin) and use the copy step as the same way.

How do I disable Clamav from downloading virus database from Internet

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

Deployment of Windows Services on Remote Servers (Different Domain)

Is there a simpler way of deploying Windows Services from TFS than using a Powershell script, run on the TFS server, which:
Stops the existing Windows Service on the remote server
Copy the file on a shared folder on the remote server (copy-item)
Starts the Windows Service on the remote
If not, can any other continuous integration/deployment tool do this better?
As the TFS server is using a domain controller which is different from the remote server, can we share a folder for a specific user? I tried to run the powershell script as a user from the target domain controller, but of course, it is not recognized as a valid user on TFS server.
At last, is there any difference on deploying on an hosted remote server or on the cloud?
Thanks,
In tasks based build system (TFS 2015 +), you can try to install Windows Service Release Tasks, which contains tasks to start and stop windows services as well as change the startup type.

Fluentd source path to tail remote files

all, I'm new to this site, and Linux. I've just installed fluentd on Linux Mint. I want to use it to tale .evl logs at remote sites (by ip address) on our network, and send an email when a certain phrase appears. I'm reading on how to set up the tail input plugin. However, in the source section of fluent.conf, how do I specify the path for a remote file?
Fluentd as of Aug 2015, doesn't support tailing the remote files (#see in_tail plugin). You probably need to copy the files from remote to local via scp or rsync. Or you can post the data remotely via http (#see in_http plugin)

Copy messages in messagequeues from Windows Server 2003 to Windows Server 2012

We are migrating from Windows Server 2003 to Windows Server 2012. There are messages in private messagequeues on Windows Server 2003 that we need to move to Windows Server 2012. It's a one-time task.
The following 3 steps corrupted messagequeues on server 2012, and I had to uninstall and reinstall Message Queuing on Server 2012.
mqbkup -b c:\msmq_backup -y (on 2003)
Copy c:\msmq_backup from 2003 to 2012.
mqbkup -r c:\msmq_backup -y (on 2012)
http://technet.microsoft.com/en-us/library/cc773213%28v=ws.10%29.aspx
http://technet.microsoft.com/en-us/library/hh875586.aspx
I access these messagequeues and messages from .NET console and ASP.NET applications using System.Messaging Namespace.
http://msdn.microsoft.com/en-us/library/system.messaging%28v=vs.110%29.aspx
Any ideas would be appreciated. Thank you.
MQBKUP is not for moving to upgraded systems as it restores the old MSMQ configuration which, as you've found, won't necessarily be compatible.
If the computername is the same, you could try straight copying the LQS and Storage folders. On startup, MSMQ checks the address in the messages. If the address matches the local computername, the message will be loaded, otherwise discarded.
Of course, this assumes the MQ file format is the same in 2012 and, unfortunately, I haven't had a chance to look.