I’m hoping to do better in the future, but for now:
https://www.pdq.com/blog/setting-up-dfs-in-your-environment/
I’m hoping to do better in the future, but for now:
https://www.pdq.com/blog/setting-up-dfs-in-your-environment/
OK, so we have that problem increasingly common, a 64-bit server, trying to serve a printer to 32-bit client machines, or vice versa. It took me a while, but here are two different methods I have needed, depending on situation.
First, see if current drivers are downloadable for this printer in the server’s mode (bit-width). If they are, we are able to use method #1, which is probably preferable, although method #2 may still work too. Here’s method #1:
If you cannot use method #1, or if there are no downloadable drivers for your printer, we go to method #2:
Some interesting items here for overall filesystem performance:
https://docs.microsoft.com/en-us/windows-server/administration/performance-tuning/role/file-server/
Open up your SQL server instance in the Studio. Go to the Properties of your instance.
Under Memory, you will see a minimum and a maximum. Set the minimum to 1024 (MB) or 2048. Reserve 4 gigabytes RAM minimum for the OS, add some more for anything else running on it, then use the rest as your maximum memory usage setting.
Also under Memory, you will see “Minimum memory per query”. Default is 1024. Set this to 2048.
Then under Processors, check “Boost SQL Server priority”.
And click OK.
Some info here:
The simplest appears to be thus:
wmic computersystem where caption='oldcomputername' rename newcomputername
If it is run from an administrative CMD and the machine is in good talking relationship with its domain controller, the PC and also AD rename will complete. If either prerequisite is not met, the rename will fail. A non-admin attempt fails with code 5, DC availability fails with 1355.
There is also tool, part of the 2003 server reskit and included later on, which can do the rename of a desktop from a domain controller:
NETDOM RENAMECOMPUTER OLDNAME /newname:NEWNAME /userd:domain\domainadmin /passwordd:password /force /reboot:0
It causes a reboot of the target machine. /reboot:0 means no delay; the number is in seconds.
Great info here:
http://woshub.com/fixing-high-memory-usage-by-metafile-on-windows-server-2008-r2/
using this for investigation:
https://technet.microsoft.com/en-us/library/ff700229.aspx
and this service for cure:
http://www.microsoft.com/en-us/download/details.aspx?id=9258
There are several tools fitting this general description, but this writer has only found one turnkey installable. This is Yacy:
Very fast, quite straightforward to set up and configure (though you’ll learn a thing or two if you’ve never thought about search very much!), almost not at all counterintuitive. It can be easily set up as either a LAN-local search server or part of its distributed WWW network.
There is a runner up, Open Search Server:
If its documentation were remotely adequate, it might be comparable, but sadly, not.
Good article, sent by the remarkable Zach Hogan:
https://sysblogging.com/2015/12/29/how-to-migrate-windows-file-server-shares-with-ntfs-permissions/
SFTP, also called SCP, is not, accurately speaking, FTP. SFTP is “SSH File Transfer”, transfer of files over the SSH protocol, and not the FTP protocol. The FTP protocol has its own excellent secure (FTPS) capabilities, FileZilla being a recommended graphical FTP server for Windows; but GUI servers for SSH are much harder to find. Happily, here is one: