Friday, 11 April 2014

Dell 3020 - UEFI bios option

Windows 8 machines with UEFI bios will ONLY Boot  Windows 8 64 bit OR Ubuntu.

Unless secure boot can be turned off and Legacy CSM GPT boot turned on it will not.

1. Boot Dos

2. Boot earlier versions of windows including 7 or Vista or XP.

3.  Boot any OS that has not paid the Fee to Microsoft for a Certificate.  Canonical Paid for the windows 8 Certificate to be in Ubuntu 12.04.3 and later versions.

When a UEFI Secure Boot system boots up Ubuntu, it will first boot a loader image. Canonical will be relying on a Microsoft key for booting this loader image from its CDs and will be signing the loader only with that key due to UEFI restrictions.

Other linux installs that rely on GPLv3 GRUB 2 boot loader will not load nor will MSDOS, IBM DOS, FREEDOS, WIN9X ETC.

This booting lockout also includes floppy disks and Usb flash drives.

http://ozlabs.org/docs/uefi-secure-boot-impact-on-linux.pdf

 Secure boot technology is now part of the new UEFI firmware specification. It is a given that Microsoft®’s Windows 8 and beyond will require secure boot to be enabled by default. UEFI secure boot is a technology integrated into the latest version (v2.3.1) of the UEFI specification. When UEFI Bios is at the 3.0 level computers will ONLY be able to boot secure boot and Windows only or Ubuntu since they paid for a Microsoft Windows 8 bootloader. CSM Legacy booting will be Gone at that time.  

Tuesday, 1 April 2014

Fwd: Webdav & Samba




Install Webdav & Samba (instructions below)


Change smb.conf to reflect correct Webdav directory

 sudo nano /etc/samba/smb.conf

Restart Samba
sudo restart smbd

Access it from Windows

\\ipadshare\foldername

Add Permissions to the folder

sudo chown -R webdav /webdav/









Webdav & Samba

Install Webdav & Samba (instructions below)


Change smb.conf to reflect correct Webdav directory

 sudo nano /etc/samba/smb.conf

Restart Samba
sudo restart smbd

Access it from Windows

\\ipadshare\foldername







Sunday, 23 March 2014

Blu3yy is still waiting for you to join Twitter...

 
Top corners image
     
 
   
 
 
 

Blu3yy is still waiting for you to join Twitter...

 
 
Accept invitation
 
     

Wednesday, 19 March 2014

Blu3yy sent you an invitation

 
Top corners image
     
 
   
 
 
 

Blu3yy has invited you to join Twitter!

 
 
Accept invitation
 
     

Monday, 10 March 2014

Re: Investigating time sync errors (Win2008 R2, Windows 7)

TIME - error on Windows 2008 R2

The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.

Time - Error

Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.

Manually configuring NTPClient to sync with external source:

w32tm /config /manualpeerlist:"time.windows.com,0x1" /syncfromflags:manual /reliable:yes /update

Access is denied (0x80070005)


STEPS

1. Stop windows time service
2. unregister tm service (w32tm /unregister)
3. register tm service (w32tm /register)
4. run w32tm /config /manualpeerlist:"time.windows.com,0x1" /syncfromflags:manual /reliable:yes /update
5. Monitor

VERIFYING TIME on Windows 2008 - See that you are getting your time from an external source - see "time2.jpg"



On 10 March 2014 11:07, Marna Marie' Strauss <mmstrauss@gmail.com> wrote:
TIME - error on Windows 2008 R2

The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.

Time - Error

Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.

Manually configuring NTPClient to sync with external source:

w32tm /config /manualpeerlist:"time.windows.com,0x1" /syncfromflags:manual /reliable:yes /update

Access is denied (0x80070005)


STEPS

1. Stop windows time service
2. unregister tm service (w32tm /unregister)
3. register tm service (w32tm /register)
4. run w32tm /config /manualpeerlist:"time.windows.com,0x1" /syncfromflags:manual /reliable:yes /update
5. Monitor


Investigating time sync errors (Win2008 R2, Windows 7)

TIME - error on Windows 2008 R2

The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.

Time - Error

Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.

Manually configuring NTPClient to sync with external source:

w32tm /config /manualpeerlist:"time.windows.com,0x1" /syncfromflags:manual /reliable:yes /update

Access is denied (0x80070005)


STEPS

1. Stop windows time service
2. unregister tm service (w32tm /unregister)
3. register tm service (w32tm /register)
4. run w32tm /config /manualpeerlist:"time.windows.com,0x1" /syncfromflags:manual /reliable:yes /update
5. Monitor