Tuesday, 29 April 2014
Windows 2008 time issue
- Log in to your PDC Server and open the command prompt.
- Stop the W32Time service: C:\>net stop w32time
- Configure the external time sources, type: C:\> w32tm /config /syncfromflags:manual /manualpeerlist:"0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org"
- Make your PDC a reliable time source for the clients. Type: C:\>w32tm /config /reliable:yes
- Start the w32time service: C:\>net start w32time
- The windows time service should begin synchronizing the time. You can check the external NTP servers in the time configuration by typing: C:\>w32tm /query /configuration
- Check the Event Viewer for any errors.
The Windows Time service (W32Time) provides network clock synchronization for computers without the need for extensive configuration.
The Windows Time service is essential to the successful operation of Kerberos version 5 authentication and, therefore, to AD DS-based authentication. Any Kerberos-aware application, including most security services, relies on time synchronization between the computers that are participating in the authentication request. AD DS domain controllers must also have synchronized clocks to help to ensure accurate data replication.
The Windows Time service is implemented in a dynamic link library called W32Time.dll. W32Time.dll is installed by default in the %Systemroot%\System32 folder during operating system setup and installation.
SET time from workstation
net time /domain:DOMAINNAME /set
Thursday, 17 April 2014
CloneZilla error
| lonezilla to image SSD fails with MBR/GPT mismatch Windows 7 Pro 64-bit is successfully installed on a 128Gb SSD drive (ADATA SP900). 'Computer Management' confirms the partition style is MBR for this drive. When using Clonezilla to take a backup image of this drive, my preferred backup method, it reports the following error: "This disk contains mismatched GPT and MBR partition: /dev/sda" As I do not use the GPT partition system, is there a 'safe' fix that will not result in a loss of data please? Thanks in advance. | |
 |   |
 2nd Oct 2013, 18:38 | #2 |
| Associate Joined: Aug 2011 Posts: 25 | Problem solved If anyone is interested, using the command line mode in Clonezilla, I removed the GPT components using gdisk: # sudo gdisk /dev/sda GPT fdisk (gdisk) version 0.7.2 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: present Found valid MBR and GPT. Which do you want to use? 1 - MBR 2 - GPT 3 - Create blank GPT Your answer: 1 Command (? for help): x Expert command (? for help): z About to wipe out GPT on /dev/sda. Proceed? (Y/N): y GPT data structures destroyed! You may now partition the disk using fdisk or other utilities. Blank out MBR? (Y/N): n <--- do NOT choose Y! MBR is unchanged. You may need to delete an EFI GPT (0xEE) partition with fdisk or another tool. All working now and Clonezilla runs without errors. |
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.