Saturday, November 17, 2018

This has worked great for initial updates of windows machines before connecting to local WSUS Server

WSUS Offline Update ...since security, time and bandwidth are money.

http://www.wsusoffline.net/

http://www.wsusoffline.net/docs/

https://www.techrepublic.com/article/how-to-use-wsus-offline-update-for-windows-clients-and-servers/


How to: Deploy WSUS to clients without AD/Domain/GP using the registry

Good information here on how to add non-domain computers to WSUS.

From https://community.spiceworks.com/how_to/2267-deploy-wsus-to-clients-without-ad-domain-gp-using-the-registry

We have a workgroup environment here and I needed a solution to provide our internal WSUS server to the clients.
So I used the way to add registry keys to our machines.

Note: the values used here working for my environment. Yours may differ. You can change them to match your needs. Please read more about it at #5 of this how-to.

9 Steps total
Step 1: Create a *.reg file (wsus-client.reg) containing this:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"AcceptTrustedPublisherCerts"=dword:00000001
"ElevateNonAdmins"=dword:00000001
"TargetGroup"="Workstations"
"TargetGroupEnabled"=dword:00000000
"WUServer"="http://your-WSUS-server:port"
"WUStatusServer"="http://your-WSUS-server:port"

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
"AUOptions"=dword:00000004
"AUPowerManagement"=dword:00000001
"AutoInstallMinorUpdates"=dword:00000001
"DetectionFrequency"=dword:0000000a
"DetectionFrequencyEnabled"=dword:00000001
"IncludeRecommendedUpdates"=dword:00000001
"NoAUAsDefaultShutdownOption"=dword:00000001
"NoAUShutdownOption"=dword:00000001
"NoAutoRebootWithLoggedOnUsers"=dword:00000001
"NoAutoUpdate"=dword:00000000
"RebootRelaunchTimeout"=dword:0000000a
"RebootRelaunchTimeoutEnabled"=dword:00000001
"RescheduleWaitTime"=dword:0000000a
"RescheduleWaitTimeEnabled"=dword:00000001
"ScheduledInstallDay"=dword:00000000
"ScheduledInstallTime"=dword:00000003
"UseWUServer"=dword:00000001

Step 2: Edit the lines:
- "WUServer"="http://your-WSUS-server:port"; and
- "WUStatusServer"="http://your-WSUS-server:port";
to match the IP address (or FQDN) of your WSUS server. IMPORTANT: remove the ";" from the end of that lines!

Examples:
"WUServer"=" http://WSUS.company.com:81 "
"WUStatusServer"=" http://WSUS.company.com:81 "

"WUServer"=" http://192.168.0.1 "
"WUStatusServer"=" http://192.168.0.1 "

"WUServer"=" http://intranet.local:8080 "
"WUStatusServer"=" http://intranet.local:8080 "

The first key is named WUServer. This registry key holds a string value which should be entered as the WSUS server’s URL.

By default, in Windows Server 2012, WSUS 4.0 uses port 8530. However, WSUS 3.0 uses port 80, by default
(How to Determine the Port Settings Used by WSUS - https://technet.microsoft.com/en-us/library/bb632477.aspx)

The other key that you will have to change is a string value named WUStatusServer. The idea behind this key is that the PC must report its status to a WSUS server so that the WSUS server knows which updates have been applied to the PC. The WUStatusServer key normally holds the exact same value as the WUServer key.

Step 3: Store the *.reg file
where the computers have access to it.

Step 4: Apply the *.reg file by:
Expand
- double click on it from the client machine (admin rights required)
OR
- put in into the login script so it will be applied at every login

Here an example for using it in a Novell Login Script (Drive Z: is here the drive needed for the login):

IF OS = "WINNT" THEN
#regedit.exe /s Z:\WSUS\wsus-client.reg
@wuauclt.exe /resetauthorization /detectnow
END

Step 5: Options:
Here some links to get more informations about the options used in the *.reg file:

- http://technet.microsoft.com/en-us/library/cc708449%28WS.10%29.aspx
- http://www.windowsnetworking.com/articles_tutorials/Registry-Keys-Tweaking-Windows-Update-Part1.html
- http://www.windowsnetworking.com/articles_tutorials/Registry-Keys-Tweaking-Windows-Update-Part2.html
- http://www.wsus.de/gpo (German - sorry)
- http://smallvoid.com/article/winnt-automatic-updates-config.html
- http://www.appdeploy.com/tips/detail.asp?id=103

Step 6: How to remove that settings from the client?
Maybe it`s needed to remove that settings for various reasons. To get the default values in the registry, just follow the next step.

Step 7: Create a *.reg file (remove-wsus-client.reg) containing this:
Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]

[-HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]

Step 8: Store the *.reg file
where the computers have access to it.

Step 9: Apply the *.reg file by:
Expand
- double click on it from the client machine (admin rights required)

That`s all. I don`t think it`s useful to add this in a login/logout script ;-) but it would work too.

I use this method for setting up a new machine even the machine will be used outside of our network after setup.
In this way the new client gets all needed updates in a shorter time frame than downloading it all via internet from Microsoft.
After finishing the setup, I remove the settings as described from #6 on.

Published: Jul 6th, 2011 · Last Updated: Aug 31st, 2018
References
WSUS Step by Step

Troubleshoot activation errors for Office for Mac 2011

https://support.office.com/en-us/article/troubleshoot-activation-errors-for-office-for-mac-2011-7db87075-632d-481b-ad25-c4dffc32fe49


Monday, September 17, 2018

Linux Mint 19 and Windows network shares

I was wondering why my Linux Mint 19 box was not letting me browse my windows network shares the same way it worked in Linux Mint 18.  Well, here are the answers, well explained.

from https://forums.linuxmint.com/viewtopic.php?f=42&t=270442

Mint 19 and Samba File Sharing Changes
Post  by altair4 » Sat Jun 02, 2018 7:52 am

Mint 19 and Samba File Sharing Changes 

The last few releases of Ubuntu introduced a number of changes to Samba itself, its Linux kernel component, and even how Ubuntu configured it.

Mint 19 as a Samba Client

[A] Are you trying to get a list of all the samba / smb servers on your network from your file manager?

Samba changed the maximum client smb dialect that it can use from SMB1 to SMB3 so that it could connect to servers that have disabled SMB1 like Win10. This inadvertently disables netbios host discovery so if you go to Network > Windows Network you will see something like Folder is Empty in Ubuntu and just a blank screen in Cinnamon, Xubuntu, etc,..

You can restore it's discovery ability by editing /etc/samba/smb.conf and right under the workgroup = WORKGROUP line add this one:
CODE: SELECT ALL

client max protocol = NT1
And then reboot. Yes, reboot.

But: If you set the max back to NT1 you will be able to see a server that has disabled SMB1 ( Win10 ) but you will not be able to access it through the file manager.

** With the default setting of SMB3 you can however still access it but you have to do so explicitly by name in your file manager ( smb://windows-host-name ) or ip address ( smb://192.168.0.100 ), or by using Connect to Server. 

If you have a problem with that please see this: Samba Browsing Problems Checklist.

** If the other machine runs Win10 you can also use this method: Win10, Linux, mDNS, and Samba File Sharing

** This change to smb3 does not impact any machines that have registered mDNS for their samba / smb shares. So if the other machine runs Ubuntu 17.10 or newer, another Mint 19 machine, or macOS you will automatically see those machines under Network - but not under Windows Network since it's not using a Windows discovery protocol.

** If the other Linux machine is using an earlier Mint or Ubuntu I would suggest adding to those machines an avahi/samba service announcement: Samba Browsing in an all Linux or Linux/OSX network

[ B] Are you using CIFS to mount your server?

The Linux kernel starting with 4.13 changed the default smb dialect that CIFS uses to SMB3 from SMB1. After 4.13.5 it's set to negotiate the version used with the server between 2.1 to 3.02 ( 3.11 in linux kernel 4.17 ). All modern SMB servers ( Win10, macOS, and Linux ) will accept SMB3 so this should not be an issue.

** What can be an issue is if you are running something with a very old version of samba like most NAS devices and there you would have to add an option to your cifs mount statement forcing it back to SMB1:
CODE: SELECT ALL

vers=1.0
Mint 19 as a Server:

First: Remember Mint doesn't install the samba server package by default any longer so install it now:
CODE: SELECT ALL

sudo apt install samba
[C1] Are the clients to this server running Linux or macOS?

Stating with Ubuntu 17.10 Samba has been configured correctly for mDNS. As soon as you install Samba your machine will become visible to all the other Linux and macOS machines by default. If you created shares on Mint19 those shares will also be visible. There is no need to make any other changes

[C2] Are the clients to this machine running Windows?

A Windows machine will have the same success or failure at discovering your machine that it did in earlier Mint versions. If you have problems see: Samba Browsing Problems Checklist.

If it is running Win10 it can always use \\mint-host-name.local or \\mint-ip-address.

Wednesday, September 12, 2018

Running batch files in windows task scheduler

Good information for starting batch files in windows ... be sure to read the comments at each page for further clarification.

From here: https://stackoverflow.com/questions/4437701/run-a-batch-file-with-windows-task-scheduler

I faced the same problem, but I found another solution without having to modify my batch script.

The only thing that I missed out is at the 'Action' settings - "Start in (Optional)" option.

Go the task properties --> Action tab --> Edit --> Fill up as below:

Action: Start a program
Program/script: path to your batch script e.g. C:\Users\beruk\bodo.bat
Add arguments (optional):
Start in (optional): Put the full path to your batch script location e.g. C:\Users\beruk\(Do not put quotes around Start In)
Then Click OK

It works for me. Good Luck!

And from here : https://stackoverflow.com/questions/20254666/keep-command-line-window-open-when-running-scheduled-task-executing-batch-file

In the Scheduled Task dialog, just before the name of the batch file it's going to run (it's labeled Program/script. You now have something like:

myscript.bat
Change it to

cmd 
Add the following to the **Add Arguments (optional) entry:

/k "C:\My Batch File Folder\MyScript.bat"
Tested on my system (Win7 64-bit), and it worked perfectly. I'm looking at the open command window it created as I type this text. :-)

Helped me!

Tuesday, September 04, 2018

Deleting too long file names in Windows 8 and larger

Good information here:

https://superuser.com/questions/755298/how-to-delete-a-file-with-a-path-too-long-to-be-deleted

Assuming you are on windows:

What I always do is use subst to create a drive letter association with part of the path.

Then go to the new drive letter and navigate to the files that have long names. You should now be able to rename/delete/etc them. The reason this works is because the path itself is no longer containing >255 chars.

To create a subst folder
Start a command prompt (no admin privileges needed)
Use cd to navigate to the folder you want to go (you can use tab to autocomplete names
type subst j: . to create the driveletter association. (instead of the . you can also type the entire path)
Now in Explorer, you have a new drive letter in This PC. Go to it and do whatever you need to do to the .cache files.
Return to your cmd window and type subst /d j: to remove the drive or alternatively, restart your pc.
EDIT: A trick I learned which can shorten this quite a bit. From the Explorer window where you have trouble, click the address bar so you can type in it, then type cmd and press Enter to start a command prompt at that location, then proceed at step 3. :)

EDIT2: Okay, this trick can be expanded even further. If you are in explorer at the right path, just type in subst j: . in the address bar and press enter. A command window will pop up, execute the command and close again, and there you go, a new drive pops up in explorer.

Friday, June 01, 2018

Netgear A6100 USB Network Adaptor in Ubuntu / Mint

From:
https://ubuntuforums.org/showthread.php?t=2235778
https://forums.linuxmint.com/viewtopic.php?t=262560

-------------------------------------------------------------------------------------
Bus 001 Device 006: ID 0846:9052 NetGear, Inc.

led me to.
http://forum.ubuntu-fr.org/viewtopic.php?id=1572411
and this led to..
https://wikidevi.com/wiki/Netgear_A6100
Which shows your device 0846:9052 NetGear
has the rtl8812au chip
and finally the chilli555 fix can be found,,
Please first do..

Code:
sudo apt-get install --reinstall linux-headers-$(uname -r) build-essential
Then go here ..
http://askubuntu.com/questions/36801...ter-ew-7822uac

From the site just above:

Please check here: https://github.com/abperiasamy/rtl8812AU_8821AU_linux On the right hand side, click 'Download ZIP.' Assuming downloads go to your Downloads folder, open the folder, right-click the zip file and select 'Extract Here.' Open a terminal and do:

cd Downloads/rtl8812AU_8821AU_linux-master
make
sudo make install
sudo modprobe 8812au
 
It 'makes' with a couple of warnings on my 13.10 system, but no errors. I can test no further since I haven't the device. This is a rather new device and we'll be very interested in your report.
Whenever a later kernel version, also known as linux image is installed by Update Manager, after you reboot, you will need to re-compile the driver:

cd Downloads/rtl8812AU_8821AU_linux-master
make clean
make
sudo make install
sudo modprobe 8812au
 
-------------------------------------------------------------------------------------
From Linux mint site:
 
The 8811au should be supported but the source code might be old, try

sudo apt install git dkms
git clone https://github.com/abperiasamy/rtl8812AU_8821AU_linux.git
cd rtl8812AU_8821AU_linux
sudo make -f Makefile.dkms install
 
Reboot

Thursday, May 31, 2018

Windows update for non-domained computers using WSUS

(Some of this might not be Win10 friendly and needs to be sifted through.)

https://community.spiceworks.com/how_to/85392-wsus-targeting-for-non-domain-computers

https://community.spiceworks.com/topic/128245-updating-computers-using-wsus-without-joining-a-domain

https://community.spiceworks.com/how_to/2267-deploy-wsus-to-clients-without-ad-domain-gp-using-the-registry

 https://community.spiceworks.com/topic/2044619-how-to-setup-wsus-in-workgroup-non-ad-environment-with-downstream-servers

 https://social.technet.microsoft.com/Forums/en-US/55d7c0c9-8217-45ed-8400-2de66a1bed84/non-domain-clients-not-downloading-from-wsus-server?forum=winserverwsus

 https://social.technet.microsoft.com/Forums/en-US/282addfe-4b62-4b6e-b005-b96454953139/wsus-security-and-configuration-for-pc-not-on-a-domain?forum=winserverwsus

 https://support.microsoft.com/en-us/help/4035760/understanding-the-windowsupdate-log-file-for-advanced-users




Wednesday, May 30, 2018

Interesting Linux apps outside of distro channels

Virtual Volumes View
http://vvvapp.sourceforge.net/

Syncthing 
https://apt.syncthing.net/
Syncthing-gtk
https://software.opensuse.org/download.html?project=home%3Akozec&package=syncthing-gtk

Virtualbox ... newer than distribution channels for the most part   https://www.virtualbox.org/wiki/Linux_Downloads

Skype
https://www.skype.com/en/get-skype/

Angry IP Scanner
http://angryip.org/download/#linux

NoMachine remote desktop
https://www.nomachine.com/download/linux&id=1

Google Applications
https://www.google.com/linuxrepositories/
https://www.google.com/chrome/

Zoom Meetings
https://support.zoom.us/hc/en-us/articles/204206269-Linux-Installation

Dropbox
https://www.dropbox.com/install-linux

Installing Virtualbox guest additions in Debian guest

From https://unix.stackexchange.com/questions/286934/how-to-install-virtualbox-guest-additions-in-a-debian-virtual-machine


Follow these steps to install the VirtualBox Guest Additions on your Linux Debian virtual machine:
  1. Open terminal and become root (su); if you have sudo enabled, you may also do for example sudo -i; see man sudo for all options):
    su
    
  2. Update APT cache:
    apt-get update
    
  3. Install the latest security updates:
    This step will upgrade all your packages, so be wise about it. Try the following steps first and they might be enough to work if not, then perform upgrade and retry.
    apt-get upgrade
    
  4. Install these required packages:
    Packages build-essential and module-assistant are both required to be able to compile the kernel modules and so when installing the VirtualBox Linux Guest Additions you must have them. So, this command will get the headers and packages (compilers and libraries) required to work. Notice, that after installing your VirtualBox Linux Guest Additions you will leave behind some packages as well as Linux headers, which you might delete afterwards or not. In my case they didn't hurt, but for the sake of system tidiness, you might want to pick up after playing.
    apt-get install build-essential module-assistant
    
  5. Configure your system for building kernel modules:
    m-a prepare
    
  6. Insert Guest Additions ISO:
    Expand menu Devices and click on Insert Guest Additions CD image...
  7. It should mount automatically, but if for any reason it doesn't:
    mount /media/cdrom
    
  8. Run the following script:
    sh /media/cdrom/VBoxLinuxAdditions.run
    
  9. Restart the system:
    reboot
    

Installing Brother HL-L2300D in Mint Linux 18.3

From https://forums.linuxmint.com/viewtopic.php?t=262049

---------------------------------------
 http://support.brother.com/g/b/download ... _as&os=128

Go there and download the first 3 files. The LPR, Cups, and installer (they just have those letters and words as part of the name)

Put them in the download folder.

Right click the installer file and extract it here and set it to run as executable using right click.

Make sure to be online for this

Then right click on the download window and open a terminal

type sudo bash linux-brprinter-installer-2.2.0-1 HL-L2300D  << This is the key that makes this work >>


then type your password and select yes by typing "y" and pressing enter


If you are using the USB cable the type "n" and press enter when it asks you for the URI. Otherwise select Y and type in the URI number. I have no idea what a URI number is.

Then it will ask you to test print.

Select yes.

For some bent reason it will say "cannot access no such file or directory" along with jibberish. Which makes no sense to me. But it will print the linux mint test page.

Then you can print as normal.