UPDATED current as of April 2014
WINDOWS 7: Deploying to Any Machine with FOG- STEP BY STEP
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/1.png[/IMG]
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/2.png[/IMG]
Introduction

This is a guide to deploying Windows 7 from FOG, in particular deploying one image to multiple hardware; desktops, laptops etc. I have written it step by step so it is easy to follow along. You may find better ways to do things and if so feel free to comment in the thread or ask questions.

Note: I am no expert! The following is just the way I have deployed Windows 7 in our environment. I’m not saying it is the only way or even the right way to do it. But this way works, as demonstrated by others and is totally unattended.

We have used this method for around two years now and it still works perfectly.

[B]What you need- Basics*[/B]

a) Some time. Don’t expect to get it right the first, second, or third time. One thing you should do is document your entire process. It’s not hard to have a text document open while working and detail what you have done as you go. Plus if your boss asks you what you’ve been doing you can show him!
b) Virtual computer software. I used VMware workstation 8, I recommend this and will be detailing the guide using workstation 8. You can download a free trial from the VMware site:
[url]https://www.vmware.com/[/url]
c) Windows AIK tools (automated install kit)- We only need Windows system manager from this:
[url]http://www.microsoft.com/download/en/details.aspx?id=5753[/url]
More info on AIK: [url]http://technet.microsoft.com/en-us/library/dd349350(WS.10).aspx[/url]
d) An ISO or DVD with windows 7 on it. For this guide I will be using Windows 7 Professional, because all our new machines come with licenses already. I will be making both an x64 and x86 SOE.
e) An external HDD or a large spare internal for the virtual machines. If external I suggest using a fast connection like esata.
d) The best physical machine you can get- dual core minimum- quad core is better, and 8GB ram.
Note: *There will be some other utilities needed along the way

[B]Step 1: Deciding on what you want[/B]

Initially I only sought to build an x64 version of windows- however I found once I got to the drivers stage that, yes surprisingly old hardware has x64 CPU support, however x64 drivers do not work well…at all. I will elaborate on this point at the drivers stage.
So in this write up I will be making both an x86 image and an x64. The only difference between the two in terms of the build is the drivers stage and of course the initial installation on the virtual machine (VM). So I will continue this tutorial detailing one build, but where the two differ I will point that out. I recommend building both at the same time so you apply changes etc to both.

[B]Step 2: Creating the Virtual Machines[/B]

From the VMware menu, select File>New virtual Machine- select custom then next. Leave hardware compatibility as Workstation 8.0- Next.
Choose “I will install the operating system later”- Next.
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/3.png[/IMG]
Set Guest operating system as Windows 7- Next. Then name your virtual Machine. Call one Windows 7 SOE x64- call the other Windows 7 SOE x86- Next. * you can only build one virtual machine at a time.
Set the cores to two as below- Next.
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/4.png[/IMG]
Give your VM 2GB of RAM if you can, or minimum 1GB- Next.
Make sure you choose “Use bridged networking”, to ensure PXE boot works correctly- Next.
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/5.png[/IMG]
Leave the I/O controller as LSI logic SAS- Next.
Choose “Create a new virtual disk”- Next.
This step is IMPORTANT. Make sure you choose the disk type as “IDE”. I found that FOG will NOT upload virtual machines with SCSI drives- which is actually what VMware recommend.-Next.
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/6.png[/IMG]
I suggest setting the disk size of 60GB. - Next- Next- Finish. Your Virtual PC is now built, but not powered on.

Now is a good time to register the client machines in FOG. It is better to do this before you begin building the image. NOTE: I found that in order to PXE boot the virtual machine, I had to create a new local user on my physical machine.
Type “lusrmgr.msc” into run and the choose users. Create a new user called “vmware_user” with the underscores. Do not set a password. Add them to the local administrators group.

[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/7.png[/IMG]

You should now be able to PXE boot to your menu. Perform a full registration of the host.
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/8.png[/IMG]
Only set the computers name- and host OS if you have this set (windows 7)- leave all other options blank.
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/9.png[/IMG]

The machine will reboot, it will attempt to boot from C:\ but no OS exists. Power the machine off again. The machine should now exist in FOG.
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/10.png[/IMG]
[B]Step 3: Installing Windows and entering Audit Mode[/B]

In VMware while the machine is off- Choose “Edit virtual machine settings”
Select CD/DVD device, then either point the machine to a physical DVD drive with win 7 in it, or directly to an ISO file. There is no need to mount the ISO if you have one. I’m using an ISO. You can download win 7 ISO’s from this page: [url]http://www.mydigitallife.info/windows-7-iso-x86-and-x64-official-direct-download-links-ultimate-professional-and-home-premium/[/url] or from TechNet if you have a subscription.
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/11.png[/IMG]
Power on the VM. It will start installing Windows 7. Choose your language/time/keyboard input: Next.
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/12.png[/IMG]
Note, the Virtual machine may seem to lag until you have installed VMware tools.
Choose “Install Now”- Accept the license terms and hit- Next.
Choose “Custom”- Select your one and only disk and hit Next.
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/13.png[/IMG]
Windows will now start installing. This may take some time. After it has installed, Windows will reboot.
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/14.png[/IMG]
[B]THIS NEXT STEP IS IMPORTANT, SO READ CAREFULLY![/B]

When the machine comes back up- DO NOT go any further. Do not name the machine etc. At this screen:
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/15.png[/IMG]
Press CTRL+SHIFT+F3. The machine will reboot and go into Audit mode. Once back up the Machine will auto log on as a local administrator with no password set. You are now in Audit mode, and it’s time to take the first of many Snapshots!
From VMware, right click the machine name and choose: Snapshot> Take snapshot. Be sure to give a brief description so you will know where you were if you need to go back. It is hugely important to utilize snapshots during this win 7 build process, I can’t stress that enough. If you make a change that stuffs something up- you can always revert to beforehand.
I suggest to then install VMware tools. From VMware menu, choose “VM> Install VMware tools”. Follow any on screen prompts from the virtual machine. After installed take another snapshot. This is useful because it improves mouse interaction and allows you to drag and drop files to the VM from your physical machine.

@Wayne-Workman I didn’t get the notifications like the first few. Forums are great, but what about social media? Facebook might work better?

Was thinking of making an ‘appliance’, basically just a ready built fog server vm… might just help people who want to get started quickly with fog? I’m just not sure if there’s any demand for it though.

Not sure what it would looks like… maybe some lightweight ubuntu build. Would people want a ‘ready to use’ version which you just turn on and then change things as you need like IP address etc? Or would it be better to maybe automate it all? Like when it logs on first time, run a script that downloads the latest trunk and starts the installer?

I need more than the 100M default size for snapins. I think the default should be higher, 90% of my snapins are over 100Mb. I found where t do it in centOS but not for Ubuntu?

Thanks

@Sebastian-Roth Yes Sebastian, I meant to write yesterday, fog is booting no probs now with the new trunk version. I am getting corruption of the image but that might be the OEM image I’m trying to upload. I’m going to try a win 10 soe today.

[B]Step 9: FOG service and sysprepping/fogprepping[/B]

[B][/B]
Now the final steps should be to:

1. Install the FOG service, navigate to:
   [url]http://fogserver/fog/client/[/url]
   And install the FOG client service. [BE SURE TO REPLACE YOUR “Hostnamechanger.dll” or your machine won’t rename and add to domain after imaging". Replace this after FOG client is installed.
2. Download and Run “FOG Prep”- This is important for uploading windows 7 machines.
   [IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/36.png[/IMG]

The virtual image almost ready to upload to FOG. The last step is to run the system preparation too. If you closed it you can access it in:
C:\Windows\System32\sysprep\sysprep
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/37.png[/IMG]
Before doing the below, I strongly suggest to take a snapshot! It’s likely you will want to re-upload the image many times before you are happy with it. Plus you can then easily add updates/changes from that snapshot position.
Have the cleanup action to go into OOBE mode, and tick generalize. Set the shutdown option to “shutdown”, then hit OK. Sysprep will start working. Once finished the machine will then shutdown. Now the next time it powers on we want to upload FOG before windows starts again. You can also take a snapshot before you run sysprep and then let it reboot without capturing it, to make sure everything works on the next boot up before uploading it to FOG.

Step 10: Creating the image in FOG
Select “Image management” in the FOG console. Then choose “new image”. Name the image-and select “Single Partition” (NTFS Only, Resizable).
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/38.png[/IMG]

Now go to your host and reference the newly made host image to your registered host machine.
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/39.png[/IMG]
Then choose “Basic Tasks” from the menu to the left. Choose “upload Image”>“Upload image”. The task will start. Fog will automatically resize the partition for upload.
Now you just need to turn your virtual machine back on, and hit F12 to ensure it network boots. If it PXE boots then FOG will grab the image and upload it! If windows starts then you have not successfully PXE booted and you need to return to your snapshot- and re run sysprep. My Final image size was approx 10GB.
You are finished!
[IMG]http://i1127.photobucket.com/albums/l629/Andrew_Hingston/40.png[/IMG]
That’s pretty much it. Now you can deploy the image to other psychical machines by the standard process. Thanks to the SAD2 tool drivers are a breeze, that said, Windows 7 and Sysprep will handle the majority of the essential drivers, but it’s nice to get the correct drivers from SAD2.
I have deployed this on many machines. Most recent machine I was testing was a Lenovo desktop, CPU i5 quad, 4GB ram, onboard graphics and I put an SSD in it and it imaged in two minutes dead (I tried another with the original mechanical drive, and it managed two minutes- five seconds)… It finished the windows deployment in another 2 minutes approx. It auto logged on and deployed SAD2 and installed drivers in around 4 minutes, then rebooted, joined the domain and renamed. All up it was probably done in around 15 minutes max.
I hope this guide will help you in some small way. I don’t think it’s possible to make a ‘one guide fits all’ for win 7 deployment, because there are just so many variables, but I hope this might help get you started. Thanks for reading!

Please feel free to comment etc below.

• A. Hingston 2012

@Wayne-Workman

Thanks Wayne.

For anyone who finds this thread, on Ubuntu, just cd to /etc/php5/apache2 then edit php.ini

Using nano to edit, find upload_max_filesize and post_max_size and increase both as desired. I increased mine to 3000M (3GB approx.)

@Tom-Elliott I booted into the live CD and ran this and this is the output. Not sure if I’m doing it right
[img]http://i.imgur.com/xxqdVop.png[/img]

Hi,
When I started I couldn’t find much information on the process. There is a lot of information but I couldn’t find any guides as such for total newbies. So now that I’ve got the hang of it I thought I’d make one for others new to FOG and Snapins. I have attached the guide as a PDF, or you can read below.

I hope it is easy to understand, and believe me it gets easier very quickly the more you do.

Thanks for looking.

[CENTER][B]A newbie’s Guide to creating a FOG snapin[/B][/CENTER]
[CENTER] [/CENTER]
[B]Introduction[/B]
If you are reading this chances are you’re not sure how to make a snapin for FOG. I will give a little introduction and also the basic process of what a Snapin does. You can also skip the below if you already know this.
[B]What is a Snapin?[/B]
Ok, so a Snapin is used to deploy programs to your computers after you have imaged them. Manually installing each program can be very tedious and time consuming. There are many ways to do this, however I’ve found this way works best for the organisation I work in, however I believe it will apply to any IT department.
Once your computer is imaging, you can specify which programs you want it to have installed. An example might be:
Anti Virus, Microsoft Office, Adobe Reader, Adobe Flash.
Generally you will likely have more, this is just an example. So now that you have specified which snapins you want your Machine to have, it will start installing them automatically once logged on after imaging. So that’s the process.
[B]How does it work?[/B]
Snapins are compressed self extracting executable files. Simple right? It is once you have done it a few times!
Essentially, you get your program installation files, (exe or msi), add them into a folder (just easier to manage) write a simple .cmd script that calls the installer to start, then compress the files into a .7zip archive, then use a program to finish it. I use “7zip SFX Maker”- [url]http://sourceforge.net/projects/sfx-maker/[/url] .
You just select the 7zip archive with SFX maker and tell it to execute the cmd script once extracted. There are a few other options you can select with SFX maker but I will detail them in the walkthrough. In my example I will make an installer for Adobe Reader X (10). Ok without further ado, let’s make a Snapin!

[B]HOW TO MAKE A SNAPIN[/B]
[B]Step 1: What you need- basics[/B]
If you haven’t already, go download and install 7zip:
[url]http://www.7-zip.org/[/url]
Ok, now you need to download 7zip SFX Maker:
[url]http://sourceforge.net/projects/sfx-maker/[/url]
SFX Maker doesn’t “install” like a normal program, you just extract then run it. So, extract SFX Maker, then move the folder to C:\Program Files (x86) and make a shortcut to “7-ZIP SFX Maker”.
We will leave SFX Maker alone for a moment.
[B]Step 2: The installer[/B]
Ok as above in this example I’m going to make an installer for Adobe Reader 10. When finished it will automatically install Adobe Reader X and make a few Registry changes to avoid some prompts. First create a folder for your installer. Call it something descriptive:

[IMG]http://i1107.photobucket.com/albums/h386/andyroo54/1.jpg[/IMG]
Download the full installer from Adobe and save it into the folder you just made:
[url]http://get.adobe.com/reader/enterprise/[/url]

[IMG]http://i1107.photobucket.com/albums/h386/andyroo54/2.jpg[/IMG]

[B][COLOR=red]You may want to test the install before you go any further to make sure it installs correctly. [/COLOR][/B]

[B]Step 3: Additional items[/B]
Now I’ve tested Adobe Reader installing and I’ve found I want to make a few changes to the registry after the install. These can be done by adding some registry entries and including them in the snapin. You may or may not want to do this yourself. I also changed units to Centimetres but will not include that in this example. For this example I want to:
Disable automatic updates
Disable protected mode (can cause some issues)
And automatically accept the EULA (end user license agreement)
You can export the registry settings by using Regedit after you have installed the program, and set the options manually in the program, see here:
[url]http://technet.microsoft.com/en-us/library/cc781982(WS.10).aspx[/url].
If you want to add these entries yourself just copy and paste the below into a text document, then name them with the extension example.reg and they will turn into registry entries. Only include everything under the line.
Disable updates:__________________________________________________________________
[B]Windows Registry Editor Version 5.00[/B]

[B][HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\10.0\FeatureLockdown][/B]
[B]“bUpdater”=dword:00000000[/B]

Disable protected:_________________________________________________________________
[B]Windows Registry Editor Version 5.00[/B]

[B][HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\10.0\Privileged][/B]
[B]“bProtectedMode”=dword:00000000[/B]

EULA:___________________________________________________________________
[B]Windows Registry Editor Version 5.00[/B]

[B][HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Reader\10.0\AdobeViewer][/B]
[B]“EULAAcceptedForBrowser”=dword:00000001[/B]

[B]Save your registry entries into the SFX-Adobe Reader X folder:[/B]

[IMG]http://i1107.photobucket.com/albums/h386/andyroo54/3.jpg[/IMG]

[B]Step 4: The script and sleep[/B]
Now we need a script. The script is responsible for installing the program, and in this case making the registry entries also. I use .cmd scripts as they are simple to write, and once you have a good one you can just modify it for other programs. Below is the script I will us. DELTE THE RED TEXT, it only serves to explain , then Copy and paste this into a notepad document, and save it as “install.cmd” then save to the SFX Adobe folder:

@ECHO OFF
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
CLS [COLOR=red](This clears the command window screen)[/COLOR]
ECHO INSTALLING ADOBE READER X DO NOT CLOSE [COLOR=red](this message will appear in a window)[/COLOR]
ECHO.
START “Adobe Reader” /wait “AdbeRdr1000_en_US.exe” /sAll /rs /msi EULA_ACCEPT=YES [COLOR=red](this calls the Adobe reader to start installing. The switches at the end help make it unattended. There are many switches)[/COLOR]
SLEEP.exe 10 [COLOR=red](this just gives the script a little time to breathe)[/COLOR]
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
CLS [COLOR=red](below are all of the registry edits as mentioned earlier) [B](( NOTE: As per the screen shot, I did originally use “REGEDIT /S” However this doesn’t work. Please use the REG IMPORT as updated below))[/B][/COLOR]
REG IMPORT Disable_protected.reg
SLEEP.exe 1
REG IMPORT Disable_updates.reg
SLEEP.exe 1
REG IMPORT Units_to_CM.reg
SLEEP.exe 1
REG IMPORT EULA.reg
ECHO INSTALLED ADOBE READER X
ECHO.
SLEEP.exe 5
EXIT [COLOR=red](ends the script)[/COLOR]
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

[B][COLOR=red]As above DON’T FORGET TO DELETE THE RED TEXT it will cause errors if you leave it in the script. [/COLOR][/B]
Now your script should look something like this when you edit it:

[IMG]http://i1107.photobucket.com/albums/h386/andyroo54/4.jpg[/IMG]

You may have noticed in the script the command line “Sleep.exe” then a number. This is a little utility to give pauses to your script. You can download it here and add it to your SFX Adobe reader folder. [url]http://www.computerhope.com/dutil.htm[/url]
If you want your PC to restart after the installation you can add the following line, fog also give you that option when uploading the snapin:
shutdown -r -c “New program installed PC must now restart”
I don’t recommend this for snapins with FOG because you really want them all to install one after the other. You can manually restart it later once all Snapins have been deployed. [B]I strongly suggest that you now test the script/install, make sure that when you run the Install.cmd it properly installs Adobe Reader X and adds the registry entries.[/B] If so then you can proceed to the next step.

[B][COLOR=#ff0000]IMPORTANT NOTE:[/COLOR][/B] If using Vista or Win 7 you must turn off UAC evaluation prompts for administrator otherwise windows will prompt for permission to install, and hold up your unattended process. To turn off, in your system image you shoud type secpol.msc into the start/run bar, then choose “local polices>security options>User account control:Behavior of the elevation prompt for administrators in Admin approval mode” and choose “Evaluate without prompting”. Also disable “User account control: Switch to the secure desktop when prompting for elevation”.

[B]STEP 5: Making the 7Zip archive[/B]
Ok that’s the hard part done! Now for the fun part! You should have all of your items together now in the one folder as below:

[IMG]http://i1107.photobucket.com/albums/h386/andyroo54/5.jpg[/IMG]

Now select them all, then right click and choose “Add to SFX-Adobe ReaderX.7z”

[IMG]http://i1107.photobucket.com/albums/h386/andyroo54/6.jpg[/IMG]

7Zip will now compress the files into a 7Zip archive. Now we will make the SFX!

[SIZE=3][COLOR=#ff0000][B]CONTINUED IN NEXT POST[/B][/COLOR][/SIZE]

[url=“/_imported_xf_attachments/0/40_A newbies Guide to creating an SFX.pdf?:”]A newbies Guide to creating an SFX.pdf[/url]

@andyroo54

I ran gparted instead.

[img]http://i.imgur.com/dvR2ImK.png[/img]

[img]http://i.imgur.com/pUJgcwZ.png[/img]

[img]http://i.imgur.com/OP3hB69.png[/img]

FYI, after using gparted, I was able to deploy the image without a CRC32 error. I’ll do some more testing to be sure! Thanks guys

@Wayne-Workman I didn’t get the notifications like the first few. Forums are great, but what about social media? Facebook might work better?

Server

• FOG Version: 1.3.0-RC-11
• OS: 14.04 LTS

Client

• Service Version: ^
• OS: Win 7

Description

Ok a little odd… we took a brand new computer never before registered in Fog. We do the normal “Perform full host registration etc” and then at the end of the registration when it asks if we want to image, we say yes.

The machine registers, but then on reboot it doesn’t image… we have to then manually deploy the image from the fog GUI.

I found a similar post here: https://forums.fogproject.org/topic/2552/after-performing-full-host-inventory-and-registration-not-automatically-imaging-after-restart

I tried what Tom said but the proxy settings were blank. This was also happening on Trunk version 7182 which I thought maybe an upgrade would fix, but still now on this RC version same issue.

I might just rebuild the server again from scratch but I was curious if this was a known issue or not?

Thanks,

@Tom-Elliott But Tom I’m getting this on every machine, desktops, laptops, etc, so it can’t be all of those machines surely? And it wouldn’t just work the next time if it was indeed bad memory.

The server is esxi vm, no errors, no other vms on that host have any issues.

Am I the only person getting these issues? I feel like I should just rebuild on another distro.

Pass complete, no errors…

Have to mark this as unsolved because it’s still happening…!

Its so odd… you deploy and get the CRC32 error, then if you deploy it again, the next time it works…? It’s random. Surely if the disk was corrupted, then it would consistently NOT work, not randomly work and randomly not work.

@andyroo54

I ran gparted instead.

[img]http://i.imgur.com/dvR2ImK.png[/img]

[img]http://i.imgur.com/pUJgcwZ.png[/img]

[img]http://i.imgur.com/OP3hB69.png[/img]

FYI, after using gparted, I was able to deploy the image without a CRC32 error. I’ll do some more testing to be sure! Thanks guys

@Tom-Elliott I booted into the live CD and ran this and this is the output. Not sure if I’m doing it right
[img]http://i.imgur.com/xxqdVop.png[/img]

@Sebastian-Roth .

[img]http://i.imgur.com/VKHFXuc.png[/img]

It’s hardware RAID in a HP DL380 server running esxi 5.5

@Sebastian-Roth It’s on a RAID 5 storage of sandisk SSD’s in a HP DL380 server.Do you think the SSD’s might be causing an issue?

[img]http://i.imgur.com/B4xpten.png[/img]

I upgraded to S VN trunk 7182

 15/04/2016 4:20 PM Service Stop requested
 15/04/2016 4:20 PM Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"unload\"\r\n}"
}
 15/04/2016 4:20 PM Bus Emmiting message on channel: Status
 15/04/2016 4:20 PM Bus Became bus server
 15/04/2016 4:20 PM Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 15/04/2016 4:20 PM Bus Emmiting message on channel: Status

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 15/04/2016 4:20 PM Client-Info Version: 0.9.12
 15/04/2016 4:20 PM Middleware::Communication URL: http://10.0.3.213/fog/management/other/ssl/srvpublic.crt
 15/04/2016 4:20 PM Middleware::Authentication ERROR: Could not get security token
 15/04/2016 4:20 PM Middleware::Authentication ERROR: Could not find file 'C:\Windows\system32\token.dat'.
 15/04/2016 4:20 PM Data::RSA FOG Server CA cert found
 15/04/2016 4:20 PM Middleware::Authentication Cert OK
 15/04/2016 4:20 PM Middleware::Communication POST URL: http://10.0.3.213/fog/management/index.php?sub=authorize
 15/04/2016 4:20 PM Middleware::Communication Response: Invalid security token
 15/04/2016 4:20 PM Service Sleeping for 120 seconds