[Thanks, Stephen]

Continue reading Windows Phone 7′s Marketplace grows faster than Android did at launch, doesn’t mean much

Windows Phone 7′s Marketplace grows faster than Android did at launch, doesn’t mean much originally appeared on Engadget on Mon, 20 Dec 2010 22:10:00 EDT. Please see our terms for use of feeds.

Permalink WMPoweruser.com  |  eWeek  | Email this | Comments

Well there is some but nothing great, more on how to turn services on and explanation on what the service can do; simple stuff like point and click ‘its now on’ which I’m not a fan of.

I want to know how it works dammit

Okay I got that off my chest, here are a few things you may find helpful:

Basically when a report is generated such as Mail Summaries it pulls the information from SQL server and then TTC generates the email and sends it via telnet socket to your mail server.

As long as your MX records are in order everything should be on its way.

Things that could stop the transport of that report are things such as:

• Required TTC services on?
• Is Mail Summary ticked in TTC configuration?
• Is relay domains being configured?
• Is your mail server recieving mail in general?
• Incorrect MX records
• Is Telnet blocked?
• Is Annonymous unitcked on your mail/hub connector in your exchange configuration?

The Microsoft Exchange connector was a problem we encountered because ‘Annonymous’ was unitcked.

At the time of writing version 7 of Lightspeed Total Traffic Control doesn’t support TLS authentication, I confirmed this with an engineer at TTC Support however does not mean it won’t be available in future revisions.

Those are a few things to check if you happen to get into a situation where you stop recieving emails from your TTC server i.e. notspam@lightspeedsystems.com or noreply@lightspeedsystems.com.

VideoTrace is a system for interactively generating realistic 3D models of objects from video—models that might be inserted into a video game, a simulation environment, or another video sequence. The user interacts with VideoTrace by tracing the shape of the object to be modelled over one or more frames of the video. By interpreting the sketch drawn by the user in light of 3D information obtained from computer vision techniques, a small number of simple 2D interactions can be used to generate a realistic 3D model. Each of the sketching operations in VideoTrace provides an intuitive and powerful means of modelling shape from video, and executes quickly enough to be used interactively. Immediate feedback allows the user to model rapidly those parts of the scene which are of interest and to the level of detail required. The combination of automated and manual reconstruction allows VideoTrace to model parts of the scene not visible, and to succeed in cases where purely automated approaches would fail.

http://punchcard.com.au/wordpress/

http://imagine-wl.com/Education/Demo/edu.html

Currently I am doing a project to get students onto Live@EDU.

With all the administration of users, groups to the side we need to implement Live into our sharepoint portal; currently running our own and down the track moving to scholaris.

Below is a project the guys at microsoft recommended I have a look at. I am still looking for other methods so I’ll comment on anything new I will find.

Project Description
The Windows Live@EDU Single Sign On project provides a middle tier WCF service, as well as SharePoint web parts and direct connectors for providing Single Sign On from your student portal into the Windows Live@EDU environment.

Windows Live@EDU Single Sign On Service

This project contains three main components, all designed to facilitate the single sign on environment for the Microsoft® Live@EDU service.

http://liveedusso.codeplex.com/

It looks like the future will consist of schools taking advantage of Live@EDU Outlook Live so I hope this articles can help you in some way.

Recommended Prerequisites

• Windows Server 2008 with updates and Internet

• Outlook Live setup with your trusted domains, MX records configured with ISP and Online.

• Domain.live.com Administrator account details

• Check the version of Windows PowerShell on your computer.

• Check the version of WinRM on your computer.

• Install the latest versions of Windows PowerShell and WinRM.

• Verify that Windows PowerShell can run scripts.

• Coffee

Links below will guide you along:

• https://signup.eduadmin.live.com/default.aspx?1&lc=3081 – Sign up for Microsoft Live@edu
• http://help.outlook.com/en-us/140/cc952756.aspx – Install and Configure Windows PowerShell
• http://help.outlook.com/en-us/140/cc952755.aspx – Connect Windows PowerShell to Outlook Live

Once you have PowerShell up to date and working you should be good to go. Ok here we go…..

Live@EDU Outlook Live – Creating Users using PowerShell, PS1 script and a CSV file.

I stumbled across the blog of Jonny on http://liveatedu.spaces.live.com regarding creation of Live@EDU mailboxes.

The video is a helpful took I recommend watching before you proceed

PowerShell Video

PLEASE READ FIRST

From: http://help.outlook.com/en-us/140/cc952756.aspx – Also mentioned at the beginning of this article.

In PowerShell: Verify that Windows PowerShell can run scripts

Click Start > All Programs > Windows PowerShell V2.

Right-click Windows PowerShell V2 and select Run as administrator. If you get a user account control prompt that asks if you would like to continue, respond Continue.

Run the following command:

Get-ExecutionPolicy

If the value returned is anything other than RemoteSigned, you need to change the value to RemoteSigned.

Note. When you set the script execution policy to RemoteSigned, you can only run scripts that you create on your computer or scripts that are signed by a trusted source.

The only way so far I have managed to get ps1 scripts to run is using the following command:

Set-ExecutionPolicy Unrestricted

Now if ExecutionPolicy command is set to ‘Unrestricted’ it will run untrusted scripts.

I tried many times trying to sign my own ps1 files however it kept spitting out errors, so proceed only if you trust the script you are about to run.

3, 2, 1, 0 …….

Some prep work to utilise video: (Copy & Paste)

• Create the folder ‘Tools’ in “C: Drive”.
• Create the folder ‘Logging’ in “c:\Tools”.
• Download the CSV_Parser.ps1 file from here
• Save it into “c:\Tools”

Create the file NewMailbox.csv in notepad & paste the following example:

Action,Type,Name,EmailAddress,FirstName,LastName,DisplayName,Password,ForceChangePassword

Add,Mailbox,TestMbx8888,TestMbx8888@yourdomain.edu,Test,TestMbx8888,Test Mbx8888,1111111,0

Add,Mailbox,TestMbx8889,TestMbx8889@yourdomain.edu,Test,TestMbx8889,Test Mbx8889,1111111,0

Add,Mailbox,TestMbx8890,TestMbx8888@yourdomain.edu,Test,TestMbx8890,Test Mbx8890,1111111,0

Add,Mailbox,TestMbx8891,TestMbx8889@yourdomain.edu,Test,TestMbx8891,Test Mbx8891,1111111,0

Add,Mailbox,TestMbx8892,TestMbx8888@yourdomain.edu,Test,TestMbx8892,Test Mbx8892,1111111,0

• Save it into ‘c:\Tools”

Open up PowerShell ISE (CTP3) and use the following cmdlet’s:

$Livecred = get-credential

• It will ask you to enter your Live@EDU account details.

c:\Tools\CSV_Parser.ps1 -UsersFile c:\Tools\NewMailbox.csv -LiveCredential $LiveCred -LogDirectory c:\Tools\Logging -ValidateAction $true

That is it, check out your Outlook Live console for changes.

Live@EDU Outlook Live – Creating groups using PowerShell, PS1 script and a CSV file.

To create groups in your Live@EDU account is pretty easy once you know how, there are other methods but I have written what has worked for me.

PLEASE READ FIRST

From: http://help.outlook.com/en-us/140/cc952756.aspx – Also mentioned at the beginning of this article.

In PowerShell: Verify that Windows PowerShell can run scripts

Click Start > All Programs > Windows PowerShell V2.

Right-click Windows PowerShell V2 and select Run as administrator. If you get a user account control prompt that asks if you would like to continue, respond Continue.

Run the following command:

Get-ExecutionPolicy

If the value returned is anything other than RemoteSigned, you need to change the value to RemoteSigned.

Note When you set the script execution policy to RemoteSigned, you can only run scripts that you create on your computer or scripts that are signed by a trusted source.

The only way so far I have managed to get ps1 scripts to run is using the following command:

Set-ExecutionPolicy Unrestricted

Now if ExecutionPolicy command is set to ‘Unrestricted’ it will run untrusted scripts.

I tried many times trying to sign my own ps1 files however it kept spitting out errors, so proceed only if you trust the script you are about to run.

3, 2, 1, 0 …….

Ok a few things to get out of the way before we get to the script: (Copy & Paste)

# Have PowerShell ISE (CTP3) opened and run the following commands:

• # Make sure ExecutionPolicy is to  ‘Unrestricted’

Set-ExecutionPolicy Unrestricted

• # Log into Live Account

$livecred = Get-Credential

• # The AllowRedirection parameter enables Outlook Live organizations all over the world to connect Windows PowerShell to Outlook Live by using the same URL.

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection

• # A progress indicator appears that shows the importing of Outlook Live commands into the client-side session of your local computer. When this process is complete, you can run Outlook Live commands.

Import-PSSession $Session

If you have manage not to get any errors you may proceed; the ‘$Session’ variable is important for the script to work successfully.

The script. (Copy & Paste into PowerShell V2 script area of console)

##### START ######

# THIS CODE IS MADE AVAILABLE AS IS, WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK
# OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER.
#
# Synopsis: This script is designed to add Distribution Groups in Exchange Labs based on a CSV file containing data.
#
# Script Name: CreateGroups.PS1
#
# Author: Original snippets of code was downloaded from http://liveatedu.spaces.live.com/Blog/cns!C76EAE4D4A509FBD!884.entry – Jonny
#
# Edited by Phil Shapcott 17th June 2009
#
#
#    Usage example:
#
#    What the command will look like with information:
#    New-DistributionGroup -Name Computers -Alias Computers -DisplayName Computer Club -Type Security

# Create into an array ($Records) using import-csv tool. ‘-path’ is the path to your CSV file, we have our files in “C:\Tools\”.
$records = import-csv -Path c:\Tools\groups.csv -OutVariable string

# Defines your CSV files columns as a Variable, below is an example of the first line of information “Computers” in groups.csv file.
foreach ($group in $records)

{

$this_name                 = $group.name  # ‘Computers’

$this_alias                   = $group.alias  # ‘Computers’

$this_displayname       = $group.displayname # ‘Computer Club’

$this_type                   = $group.type   # ‘Security’ group
# Create distribution group – assigning result to variable to avoid listing the new object
%{Invoke-Command -Session $Session {param ($this_name,$this_alias,$this_displayname,$this_type) New-DistributionGroup -Name $this_name -Alias $this_alias -DisplayName $this_displayname -Type $this_type}-arg $this_name,$this_alias,$this_displayname,$this_type} > $results

}

##### END ######

The CSV file example – groups.csv

The CSV file is pretty simple as well just copy the text into a notepad file and save it as groups.csv.

Save all files in “c:\Tools” folder you created earlier when creating mailboxes.

Name,Alias,DisplayName,Type

Computers,Computers,Computer Club,Security

English,English,English Faculty,Security

PRESS ‘PLAY’ (Run Script)

When you’re finihsed using the Outlook Live serve-side session, always disconnect windows PowerShell from Outlook Live.

For example, to disconnect f rom the server-side session that is defined by the $Session variable.

Remove-PSSession $Session

Credits

Jonny @ Live Spaces, Microsoft Help and Connect Site and Adam Bradley for phone support

Cheers,

Phil

I must say it looked like a toy a first glance however after having a play with it the whole kit is a well balanced machine.

You notice there are no exhuast holes anywhere so if you manage to put the laptop on water or other type of moisture you are sure not to get it wet inside.

Rubber in all the right places and utilizing a touch screen the LatitudeTm 2100 was something I can see being used in a school.

The touch screen was responsive and unlucky for me only manage to play the physic game, so I’m not sure how it will perform on the network.

The keyboard was nice to use and I didn’t feel like I had to change my comfort zone just to type something, unlike the Dell Mini 9.

Now these are not final pricing however just a quick quote it was gestimated around $600.00 AUD for basic model which includes 1GB Ram no webcam and 1 year warranty from memory.

Moving up to 2gb RAM, webcam and extended warranty probably around $800.00 AUD – Please don’t quote me.

We couldn’t get a price on the managed trolley so as soon as I hear what we are looking at I’ll post something up.

[nggallery id=3]

Cheers

Phil

We will follow the version 2.2 HowTo from http://wiki.hyber.dk/doku.php with a few modifications and comments on the setup process.

Requirements

Hardware

• 2 x boxes that meet the minimum spec of Openfiler’s hardware specifications.
• 2 x ethernet interfaces in each box
• Openfiler 2.3 installation media.
• Both boxes should have the same size drives in each to avoid any replication inconsistencies.

Software

• Install Openfiler 2.3 on both boxes utilising a disk setup such as the following:
  • 3gig /
  • 512meg swap
  • 300meg partition for cluster_metadata DRBD
  • Data partition configured as an unmounted LVM (this will be DRBD vg0_drbd)

[root@filer1 ~]# fdisk -l

Disk /dev/hdb: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdb1   *           1         382     3068383+  83  Linux
/dev/hdb2             383        4206    30716280   8e  Linux LVM
/dev/hdb3            4207        4239      265072+  82  Linux swap / Solaris
/dev/hdb4            4240        4276      297202+  83  Linux

Network

As you are using two network interfaces on each box, you need to select a range of IP addresses you want to use. The first interface is used to talk to your network… this is what your computers will see when they talk to your NAS/SAN.

The second interface is used for the DRBD data replication (dedicated interface) between the two filers. Ideally this interface has at least a gigabit of bandwidth, but it does work on 100mbit (depending on how much data you are putting through your NAS/SAN).

One thing to note in High Availability is you will need three IP addresses allocated to your cluster. The first IP address is the address that all of the computers on your network will talk to. Depending on which of your filers is Primary at the time, it will be configured to use this IP address. In an event of a fail over, the Secondary filer will become Primary and take over this IP address.

The other two IP addresses are used purely for administration, so you can directly communicate with each filer.

So, as an example, we will use a 192.168.8.0/24 subnet on our first interfaces, and 192.168.9.0/29 on the second interface.

So we can allocate the following:

• filer1
  • LAN Interface (eth0) 192.168.8.11
  • Replication Interface (eth1) 192.168.9.11

• filer2
  • LAN Interface (eth0) 192.168.8.12
  • Replication Interface (eth1) 192.168.9.12

• HA NAS/SAN Address (eth0) 192.168.8.10

Note: The Heartbeat service controls the HA Address, so DO NOT declare this address in your network config scripts… it will be declared when we configure Heartbeat.

Hostname setup

We want both filers to be able to recognise each other. As Openfiler works off it’s FQDN (Fully Qualified Domain Name), we will use that.

On filer1:

Modify our /etc/hosts (on filer1):

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               filer1 localhost.localdomain localhost
192.168.8.12             filer2

On filer2:

Modify our /etc/hosts (on filer2):

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               filer2 localhost.localdomain localhost
192.168.8.11             filer1

SSH Shared keys

We wan the two boxes to talk to each other without having to use a password. So, we will use SSH shared keys as mentioned in the Openfiler 2.2 Howto:

On filer1:

Hit enter at the prompts (we don’t want to set a password on the key).

On filer2:

Hit enter at the prompts (we don’t want to set a password on the key).

The above command will generate a file called “id_dsa.pub” in ~/.ssh/, which is the public key we need to copy over to our other filer:

Configure DRBD

DRBD is what we will use to keep the data between the two filers consistent. DRBD allows us to run a RAID-1 (mirror) over the network, so if one host goes down, the other can come up in it’s place without having inconsistent data (that’s the theory anyway).

On filer1:

Then we make our drbd.conf (version like the following:

global {
    # minor-count 64;
    # dialog-refresh 5; # 5 seconds
    # disable-ip-verification;
    usage-count ask;
}

common {
  syncer { rate 100M; }
}

resource cluster_metadata {

  protocol C;

  handlers {
    pri-on-incon-degr "echo O > /proc/sysrq-trigger ; halt -f";
    pri-lost-after-sb "echo O > /proc/sysrq-trigger ; halt -f";
    local-io-error "echo O > /proc/sysrq-trigger ; halt -f";
#    outdate-peer "/usr/sbin/drbd-peer-outdater";
  }

 startup {
    # wfc-timeout  0;
    degr-wfc-timeout 120;    # 2 minutes.
  }

  disk {
    on-io-error   detach;

  }

  net {
    after-sb-0pri disconnect;
    after-sb-1pri disconnect;
    after-sb-2pri disconnect;
    rr-conflict disconnect;
  }

  syncer {
#    rate 10M;
#    after "r2";
    al-extents 257;
  }

  on filer1 {
    device     /dev/drbd0;
    disk       /dev/sda3;
    address    192.168.9.11:7788;
    meta-disk internal;
 }

   on filer2 {
    device    /dev/drbd0;
    disk      /dev/sda3;
    address   192.168.9.12:7788;
    meta-disk internal;
  }
}

resource vg0_drbd {

  protocol C;
  startup {
    wfc-timeout         0;  ## Infinite!
    degr-wfc-timeout  120;  ## 2 minutes.
  }

  disk {
    on-io-error detach;
  }

  net {
    # timeout           60;
    # connect-int       10;
    # ping-int          10;
    # max-buffers     2048;
    # max-epoch-size  2048;
  }

  syncer {
  after "cluster_metadata";
  }

 on filer1 {
  device     /dev/drbd1;
  disk       /dev/sda5;
  address    192.168.9.11:7789;
  meta-disk internal;
  }

  on filer2 {
  device    /dev/drbd1;
  disk      /dev/sda5;
  address   192.168.9.12:7789;
  meta-disk internal;
  }
}

Take note of the “disk” variable, as these partitions may be different on your filers. Basically just need to make sure the 300meg partitions are used for cluster_metadata and the LVM partition is used for our vg0_drbd.

We get to use /dev/drbd1 as a PV (Physical Volume) for our LVM, which may not sound that exiting if you’re not used to using LVMs, but it allows us to have a dynamic volume control of our data volumes, on top of a network RAID1 device (/dev/drbd1).

• More information on LVM here.

Both hosts need the SAME drbd.conf, so we overwrite filer2′s config with our modified filer1 configuration:

Initialise metadata on /dev/drbd0 (cluster_metadata) and /dev/drbd1 (vg0_drbd) on both filers:

We can now start DRBD on both hosts:

If all goes well, they should connect and you should be able to run “service drbd status” and get a result similar to the following:

So, once both drbd resources are connected and both filers are in Secondary state (as above), we need to set a Primary filer… which we will make filer1:

This should give you a status result of something like the following:

Enable DRBD to startup at boot:

We now create our cluster_metadata filesystem. We use this 300meg partition to keep all of the Openfiler configuration data and the data for the services we want to be available in HA (eg. NFS, iSCSI, SMB).

We don’t add this partition to an /etc/fstab, as like our HA Interface, this is managed by Heartbeat… we will configure this shortly.

Configure LVM Partition

As mentioned before, we create our /dev/drbd1 as a PV (Physical Volume) for our data volume group, which we then use to create Logical Volumes for our data.

First we need to edit /etc/lvm/lvm.conf and modify the filter line:
From:

filter = [ "a/.*/" ]

To:

filter = [ "r|/dev/sda5|" ]

Note: Change /dev/sda5 to reflect the partition of your LVM, as it may be different. Also remember to apply these changes on both filer1 and filer2.

My understanding of this is so when the host scans for LVM partitions, it excludes our LVM partition, as this seems to cause problems with drbd consistency when this filter is not enabled.

Create our LVM Physical Volume (we only do this on our Primary filer, as it will replicate to the Second filer via drbd):

Configure Heartbeat

As mentioned before, Heartbeat controls our fail_over between hosts. Basically the two filers run the Heartbeat service, that sends out a heartbeat pulse on our secondary interface (eth1). If one of the filers dies, then Heartbeat detects this and roles over the surviving filer to Primary (if it wasn’t already) using startup scripts available in /etc/ha.d/resources.d.

We need to make modifications to /etc/ha.d/ha.cf and /etc/ha.d/authkeys. Make sure you make these changes on both filers.

In /etc/ha.d/authkeys, add:

You may have to actually create the /etc/ha.d/authkeys file, as it does not appear to exist in Openfiler 2.3.

We also need restrict permissions to authkeys to just “root”:

Now we create a /etc/ha.d/ha.cf on both filers (needs to be identical on both, just like /etc/drbd.conf.

Enable Heartbeat to startup at boot:

Openfiler data configuration

As mentioned above, we have created a 300meg partition to keep our configuration and HA services available when we do a fail_over. To get this working, we copy our services and Openfiler config data over to our new partition – symbolically linking it back to it’s original location. If this does not make much sense now, it should be a little clearer when we start testing the fail_over of services.

filer1:

We then edit our /opt/openfiler.local/etc/rsync.xml file:

filer2:

root@filer2 ~# mkdir /cluster_metadata
root@filer2 ~# mv /opt/openfiler/ /opt/openfiler.local
root@filer2 ~# ln -s /cluster_metadata/opt/openfiler /opt/openfiler

Change the /opt/openfiler.local/etc/rsync.xml to reflect below:

Heartbeat Cluster configuration

We then modify the /cluster_metadata/opt/openfiler/etc/cluster.xml config file. This config file generates our /etc/ha.d/haresources file, which tells Heartbeat what we want it to do in an event of a fail_over.

filer1 Only:

<xml version="1.0" >
<cluster>
   <clustering state="on" />
   <nodename value="filer1" />
   <resource value="MailTo::root@localhost::ClusterFailover"/>
   <resource value="IPaddr::192.168.8.10/24" />
   <resource value="drbddisk::" />
   <resource value="LVM::vg0_drbd" />
   <resource value="Filesystem::/dev/drbd0::/cluster_metadata::ext3::defaults,noatime" />
   <resource value="MakeMounts" />
</cluster>

Note how we have declared the HA IP Address here (192.168.8.10). As mentioned before, Heartbeat controls both the setup of the network interface and the mounting of our LVM VG and /cluster_metadata.

Samba and NFS Support

Modify Samba and NFS so it’s available on our /cluster_metadata drbd resource.

filer1:

Note: We have moved /var/spool/samba into /cluster_metadata, which is only a 300meg partition. So, if you put some large print jobs through Samba, you will find the free space on this volume will get eaten up pretty quickly. So, if this is the case, you may want to create a separate DRBD resource for your /var directory. Or you may want to reconsider hosting your print services on a server that isn’t your SAN/NAS.

filer2:

iSCSI Support

filer1:

filer2:

FTP Support

filer1:

filer2:

Configure Volume Group

filer1:

Create a Volume group from our /dev/drbd1:

Note: If you plan on using Windows to connect your iSCSI targets, do not use the “_” character or any other special characters when creating your Volume group.

Once the Heartbeat service has been configured and started (see below), you should be able to use the Openfiler web administration on https://192.168.8.10:446 to create LVM volumes and to export them via iSCSI etc.

Starting Heartbeat and first-time configuration

In order to get Openfiler to write the /etc/ha.d/haresources file based on the cluster.xml config file, we need to restart the Openfiler service and then log onto the web interface (using the Primary filer’s direct IP) and click on System -> HA Cluster Setup.

Make sure you do this on the Primary filer (assumably filer1).

After Openfiler restarts and you log onto the web interface, it should have a whole heap of values that reflect the clustes.xml file. With any luck, Openfiler has written this file out to /etc/ha.d/haresources. If haresources exist, you should be right to copy it over to filer2.

Before we can start Heartbeat we must create a volume for our heartbeat to start (Otherwise HA will fail to start).

When you log onto the web interface and activate a service such as NFS or iSCSI. this will force Openfiler to rewrite the /etc/ha.d/haresources file. You will then need to scp this file over to the second filer as follows:

Since we have added heartbeat to our start up scripts earlier, we should be right to reboot filer1 then after that to reboot filer2.

If all goes to plan you should be able to access the primary filer with your web browser via https://192.168.8.10:446 (the High Available ip address). You can then remove the ‘StartVolume’ you created above and create any other volumes you need via the web interface (Make sure you add one in before restarting otherwise HA will fail to start)

If the webserver does not work for any reason a good place to look for errors is in /var/log/ha-log this should allow you to work out where the problem may be.

Note:

The rsync configuration is meant to synchronise changes between the two filers, but from observation this does not appear to happen. So, if you update your clusters.xml file, make sure you put the re-generated haresources file on both filers. Do not modify /etc/ha.d/haresources directly, as it will get overwritten. Always use /cluster_metadata/opt/openfiler/etc/cluster.xml.

Also it is a good idea to copy over the /etc/ha.d/haresources file everytime you change your lvm volumes as this can alter the haresources file and prevent the second filer from failing over.

We have filed a bug report which has since been fixed, I am yet to try just updating this file to see if it works or not.

https://project.openfiler.com/tracker/ticket/791

Software updates

Note from the 2.2 HA Cluster Guide:

Not sure if the second filer is meant to be updated by becoming Primary and updating as the note above suggests for the first filer. Assumably this would not cause any problems, but at this stage it is something we have not tested.

Credits

We would like to acknowledge that this HowTo is heavily based on the Openfiler 2.2 HA Cluster Guide. Please make sure this is signified in all reproductions of this documentation. We have copied information from the 2.2 HA Cluster Guide with an understanding it is a public domain document. If this is not the case, please notify us and we will correct this.

The article is licensed under the terms of the GNU FDL.

Don’t you hate getting lost? Hang on I’ll use my GPS.

Of all the times I needed to go to Brisbane I thought having my new Palm Treo Pro would save me from the labyrinth of Brisbane Queensland streets; denied.

Some how the GPS was not initiating at all and GPRS can only get you so far, so Google Maps and WhereIS where saying I am within 400m of location LOST :S Grrr!.

Even though this is not the “FIX” I have figured out how to get it working when I need it. I tried quite a few things from other forums however there seems to be a few revisions of the phone.

What you will need to initiate the GPS and find out where the hell you are:

• GPS Test - I downloaded it from PocketGear but you can find it via google.
• Google Maps for Windows Mobile – You can download this via your mobile or internet, just make sure you have the right CAB file.

Okay now when you have downloaded, installed and sync’d those applications to your mobile phone just these easy steps below.

Prerequisites :

• Let windows mobile look after GPS data for your applications, I have used COM 4;

• Make sure you are outside for a better signal;

• Be sure to have your 3G, Next G, GPRS, HSDPA AKA Internet connection on;

• And download current data via Quick GPS program on your phone.

Step 1:

Open application GPS Test in your programs folder.

The program will scan the com ports and standard baud rate should be set for you. I waited for satellites to be found and minimized the app, took 3-4 seconds.

Step 2:

Open Google Maps and make sure to select ‘Use GPS’ and that is it.

Your Google Maps should already be using windows to get GPS data feed.

There you go pretty simple eh?  If you find a better way or an actual fix I would love to know and hear your comments

Phil

Below are steps taken to backup database, install Adventnet on another server, restore database and switch the service on.

Adventnet Service Desk runs on MySQL, they provide tools for you to manage your database.

Tools located in:

%programfiles%AdventNetMEServiceDesk. or where ever you have installed it.

Backup the database and remember what version of the database you are using.

You can check the version under the ‘about’ button on the web page.

Go to ‘Start Menu’

+ Programs
+ ManageEngine ServiceDesk Plus
+ and select ‘Backup Data’

This is automated…….

When that is done the backup should be located usually here:

%programfiles%AdventNetMEServiceDeskbackup

Example of filename: ‘backup_servicedesk_6006_fullbackup_06_08_2007_15_36.data’

Note: Remember the location of database backup you will need it on new server.

To proceed all you need to make sure is you have the programs correct build and version to restore database.

For us its:
Version : 6.0.0
Build Number : 6006

So when you download the program download package from here:

http://manageengine.adventnet.com/products/service-desk/index.html

Service pack are located here:

http://manageengine.adventnet.com/products/service-desk/service-packs.html

When installing the package make sure you have the license code ready.

Ok now, install the program and service packs until you have the same version running.

Add the license code and apply.

Locate %programfiles&AdventNetMEServiceDeskbin and open the tool ‘restoreData.bat’.

A window will open and just follow the prompts, all you need is the location of the backed up database.

Restart services and you should have your helpdesk back online.