Sometimes Seagate DiscWizard insists on rebooting, even if you’re cloning between two non-system drives. It is worth checking the state of the target drive. I found that even with no partitions, a target drive with a GPT partition table caused this issue. Solved by firing up diskpart:
list disk
select disk {number}
clean
This wipes the partition table (and consequently the disk appears in the Disk Management console as not initialized). DiscWizard should then clone to it without complaints.
If you are using Outlook it’s reasonably straightforward to access additional mailboxes on your Exchange mailserver. Using other clients it’s a bit more obscure. The Glasgow Exchange server can be accessed via IMAP (although it’s best to use the native exchange protocols when you can). To access a mailbox called mail_box use these settings (using Thunderbird as an example):
Note that when using an Apple or Android phone, you can access your primary mailbox using the Exchange protocol (and it’s recommended to do so). However, this is a reduced functionality mobile version which does not give access to additional mailboxes. For these, you have to use an IMAP connection (i.e. set up an additional mail account and use the settings above).
Had a situation that seems to be fairly common – get laptop, uninstall “Get Office” program, install Office 2016 and activate using KMS server, which seems to work fine. Then when you fire up one of the programs you get the “Lets get started” screen. You can close this and it works ok, but it is annoying.
To fix this see https://support.microsoft.com/en-us/kb/3170450 (deleting a couple of registry keys that make Office think it’s still in OEM mode).
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\16.0\Common\OEM
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\Common\OEM
Install ruby-full:
sudo apt-get install ruby-full
Install ruby-ffi
apt-get install ruby-ffi
Install Jekyll
gem install --http-proxy http://wwwcache.gla.ac.uk:8080 jekyll
install node.js
apt-get install nodejs
Should then work for normal user.
Quick test – (from https://www.digitalocean.com/community/tutorials/how-to-deploy-jekyll-blogs-with-git)
jekyll new awesomeblogThis will create an awesomeblog directory containing the configuration files, posts directory and other required bits.
cd awesomeblog jekyll serve
Jekyll will build your blog, and after a few seconds you should be able to visit http://host:4000 in your browser. Or skip the serve bit and check in the _site subdirectory.
To get git working with this create the git repository, go into the hooks subdirectory and create a post-receive script like this (again from https://www.digitalocean.com/community/tutorials/how-to-deploy-jekyll-blogs-with-git)
#!/bin/bash -l
GIT_REPO=$HOME/repos/awesomeblog.git
TMP_GIT_CLONE=$HOME/tmp/git/awesomeblog
PUBLIC_WWW=/var/www/awesomeblog
git clone $GIT_REPO $TMP_GIT_CLONE
jekyll build --source $TMP_GIT_CLONE --destination $PUBLIC_WWW
rm -Rf $TMP_GIT_CLONE
exitor /var/www/html/awesomeblog for apache on Debian 8.
If running normal raspbian edit the file /etc/network/interfaces to add in two blocks:
iface eth0 inet dhcp
and
iface eth0 inet static
address 169.254.210.230
netmask 255.255.0.0
Comment out the block not in use. For networks that have a dhcp server running use the first block, for connecting to a Windows computer via a private network use the second (If Windows connects to a network, is set to obtain an address automatically and can’t get one then it self-assigns a 169.254.x.y address). Static address can be anything of the form 169.254.x.y.
Full example file:
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto lo iface lo inet loopback auto eth0 allow-hotplug eth0 # Comment out this block when connected to laptop #iface eth0 inet dhcp # Comment out this block when connected to building network (or any network with dhcp) iface eth0 inet static address 169.254.210.230 netmask 255.255.0.0 allow-hotplug wlan0 iface wlan0 inet manual wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf allow-hotplug wlan1 iface wlan1 inet manual wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
Ran into a couple of problems here:
Default Debian behaviour is to mount cd’s with noexec option. Thus you get permission denied even as root when you try to run the install script. Solution; remount cd:
sudo mount -o remount,exec,ro /media/cdrom0
or whatever path the cd is mounted at. You need the ro otherwise it complains.
Other more general problem: sudo ./install just results in Installing... Finished and a silent fail. In the old days using gksudo fixed this but apparently it’s deprecated now. It does work when running as normal user, so tried:
sudo -E ./install
this worked correctly.
The Talysurf software on the laptop in the upper JIF lab sometimes fails to find it’s licence. This is usually because it only checks the license against the first network interface it finds, which is often the WiFi interface (the license is locked to the cabled ethernet interface).
The solution is to disable the wireless interface in the network interfaces window.
First user in Ubuntu 14.04.3 has membership of groups:
Another user created as administrator from the GUI gets:
We had a problem with a couple of users who kept having synchronisation problems with an Exchange (2010) server, using Outlook 2010. Some mail would not appear in mailboxes, but would appear in the web client. The sync would claim to complete ok, but looking at the Sync Issues folder there were a lot of messages of the form:
13:22:28 Error Synchronizing Hierarchy for Mailbox 'TeamShared' 13:22:28 [80040305-54A-4DE-1900] 13:22:28 Your server administrator has limited the number of items you can open simultaneously. Try closing messages you have opened or removing attachments and images from unsent messages you are composing.
This can occur if the secondary mailbox has a a lot of folders, which this one does – there’s a big tree of stuff in there. To solve this we turned off caching of the secondary mailbox. The details of the problem and the various workarounds are given at:
Performance problems when you try to access folders in a secondary mailbox in Outlook
See https://weakdh.org for the problem – 1024 bit Diffie-Hellman keys are potentially breakable (the ‘logjam’ vulnerability). This can be fixed in Apache 2.4 by pointing it at a custom key, but up to recently ver 2.2 was vulnerable. The issue was fixed in apache 2.2.22-13+deb7u5, which allows a custom DH key to be appended to the server certificate. To use this in Debian 7:
Update to apache 2.2.22-13+deb7u5 or higher.
Generate a new Diffie-Hellman group using
openssl dhparam -out dhparams.pem 2048
Find where the appropriate server certificate file is – standard debian setup specifies this in
/etc/apache2/sites-available/default-ssl
Append the DH group to the server certificate
cat dhparams.pem >> server_certificate.pem
The resulting file should look like
-----BEGIN CERTIFICATE----- stuff -----END CERTIFICATE----- -----BEGIN DH PARAMETERS----- more stuff -----END DH PARAMETERS-----
Restart Apache.
Checking this using the https://www.ssllabs.com/ssltest/ shows DH 2048 bits