Users logging on with local profile instead of roaming profile

I had a situation where users who should be logging on with roaming profiles loaded from a DFS share, were getting logged on with a local profile.
After browsing the logs, we could see that the profile wouldn’t get loaded because of a slow network link.
roam1

Which could be the case since users switch offices all the time.
The default policy is to check wether a slow link exists (500kb by default) and if so, windows will log you on with a local or cached profile.

To disable the slow link detection, you need to edit/create a gpo , Computer settings\Policies\Administrative Templates\System\Group Policy
roam2 
Now you need to enable the policy and set it to “0” to disable detection,or define a speed you like.
roam3

Now when this is done, you also need to modify another policy under the user profile section (Computer settings\Policies\Administrative Templates\System\User Profiles)
You only need to enable the 2 marked in the screenshot, the other ones I enabled are not for this issue.

roam4

Error 0×80070718 when opening pst or archive in Outlook

When trying to open an archive or any other PST file you can get the 0×80070718 error. This error refers to not enough disk space or quota to open the said file.
In case you are using disk quota, check the settings. In my case we were using offline files, and the quota there needed to be adjusted. To do so:

  1. Open control panel and click “sync center”
    sync1
  2. Now click “manage offline files”
    sync2
  3. A dialog will open and you can choose “disk usage”
    From there you can view the current use, which will be quite large if you’re seeing this issue.
    Then you can also choose to change the quota
    sync3 
  4. Now when you can use the drag button to change the quota to your liking, as well as the quota for temp files.
    sync4

How to create a searchable phonebook for yealink with 3CX

As you know or may not know 3CX does have a “company phonebook” which gets deployed to the serveral brands of phones with phoneprovisioning, including Yealink. However the problem is that this phonebook is not searchable , so when you have a phonebook with several hundred entries it will be a pain in the ass to find someone. Also the 3CX phonebook will only have one number per entry while the Yealink itself allows for more then 1 number per entry (Fixed/Mobile/office etc…)

So I’ll show you how to create a phonebook file, and how to deploy it to the phones using 3CX phone provisioning.
You can even add pictures if you like :-) .

What you’ll need:

  • A 3CX server & use autoprovisioning
  • 7zip or some other software to create .tar files
  • Yealink phones (I will be using the T38 since it can display pictures)
  • Notepad++ or any other editor will do

So let’s start.You need to create a file for the yealink to use. The Yealink phone expects a Contact.tar file and this file should include several files (ContactData.xml (this contains the actual entries and “photo.tar” which contains the photos.

  • Create the ContactData.xml file by creating a new text file. The file structure should be as follows.

    <?xml version=”1.0″ encoding=”UTF-8″?>
    <contactData>
    <group>

    <contact sDisplayName=”SOMECONTACT” sOfficeNumber=”SOMENUMBER sMobilNumber=”SOMEMOBILE”
    sOtherNumber=”" sLine=”" sRing=”" group=”" photoDefault=”SOMEPHOTO.jpg”
    photoSelect=”0″ />

    </group>
    </contactData>

    Enter alle the entries by copying the entry between “<group>” and “</group”> and modify for all the entries you need. You can script this as well but that’s not for today.
    Note that the “photoDefault=…” entry should match the filename you’re using for the actual photo. But more on that later. When you’re done with the file save it as “ContactData.xml”

Yealink1

  • Now you need to create a folder containing the photos (if you don’t wish to use photos you can just create an empty folder)
    So create a new folder called “photo” and put all the photos in there for the contacts. It’s important the filename matches the value you put at “photodefault=” exactly, including the extension.

 

  • Now you need to create a tar file of the “photo” folder. As described above 7zip will do the trick. So right click your “photo” folder , choose 7zip and “add to archive” then select .tar as the type and click OK.

Yealink2

  • Now you should have both a “ContactData.xml” and a “photo.tar” file. Now you need to create a new folder called “contact” again this is case sensitive.
    Then move both the files in the “contact” folder and now you need to tar this to a file “contact.tar”

Yealink3

  • Now you have the file you need to put it in the 3CX provisioning folder (C:\ProgramData\3CX\Data\Http\Interface\provisioning)

Yealink4

  • So now we need to tell the phones where to get the file by editing the provisioning template in 3CX.
    Open the 3CX management console , go to settings , provisioning templates, and select your Yealink model.
    Now add the following line somewhere in the template.

    local_contact.data.url =http://YOURPBX:YOURPORT/provisioning/contact.tar

Yealink5

So now you should be done , when applying the provisioning template to the phone it should download the contact file and extract it in the local directory.
In case it doesn’t seem to work for you then just leave a message and I’ll try to help you out.

     

     

How to configure LDAP phonebook on Aastra 620d/622d

A quick how to on how to configure and LDAP phonebook on the Aastra handsets in combination with the RFP antennas.

  • Log into the webinterface of the OMM. Navigate to “system features” , “directory” and click “New”

ldap1

  • Now a new window will open and you need to specify the settings.

ldap2

When you’re done the phone should have a new phonebook and you are able to search the LDAP users.

Note: It is important to select the correct searchtype, otherwise it will not turn up anything!

How to configure NTP on the Aastra RFP 32/35 IP & 620d/622d handsets

Here’s a short tutorial on how to configure an NTP timeserver on your Aastra RFP IP antennas, and deploy it to the handsets. I used the RFP 32/35 IP for this in combination with the Aastra 620d/622d handsets.
But I think the procedure would be the same for any other and future models.
Anyway let’s get started.

 

  • Use the configuration tool to load the config of the antenna. Then click “add parameter” in the top of the screen.

aastra1

  • Now you need to add the “DNS server address” from the drop down list (in case you didn’t already) and then the “NTP server name”.

aastra2

  • Now that you added the parameter(s) you should have some extra fields, so enter the correct info in the fields and click “Send config.”

aastra3

So after that the config tool should say “ok” and that should be it.

iTunes store crashes with IOS 7.0.4

After applying the update to IOS 7.0.4 from IOS 6 then iTunes store seemed to be sluggish and crashing constantly.
When searching songs and playing one, the screen goes black and returns to the home screen.
The quick and easy fix was to log in & out off itunes/app store.

To do so:

  • Quit the iTunes app by doubletapping the home button and swiping the iTunes app upwards.
  • Go to settings
  • iTunes & App Store
  • click your apple ID
  • Choose “sign out”
  • Sign in again

This should fix the problem.

Veeam: The specified network resource or device is no longer available

I had a problem with Veeam in combination with Hyper-V cluster and an Equallogic SAN. All backups would run fine using storage snapshots , except for one of them. Veeam would run the job but one of the VHDs for the vm could not be backed up and Veeam would fail with the shady error:

18/11/2013 17:00:24 :: Processing ‘VM’ Error: Client error: The specified network resource or device is no longer available. Failed to read data from the file [\\?\Volume{f0c726da-445d-11e3-8b10-91d33815ae43}\VM.vhd].
Failed to read data from the file [\\?\Volume{f0c726da-445d-11e3-8b10-91d33815ae43}\VM.vhd].”Exception from server: The specified network resource or device is no longer available.

Now when looking at the Event log of the Hyper-V host which hosts the VM I would see these errors regarding VSS with IDs: 12329 &13230  during the job:

This is the 12329 error:

Volume Shadow Copy Warning: A plug-and-play devnode could not be found for the volume while attempting to restart or remove the associated device.  The function GetHiddenVolumeDevinfo failed with 0×0000000000000002. The operation will be continue, however some state associated with this volume may not be cleaned up.

And then for the 12330:

Volume Shadow Copy Warning: The hardware shadow-copy volume \\?\Volume{f0c725f5-445d-11e3-8b10-91d33815ae43} disappeared unexpectedly. Check for any event logs reported by Plug And Play, by the hardware provider, or by volsnap

This last one gives us a clue about what’s going. I got a feeling that the Equallogic was in it since it talks about HW Snapshots disappearing. And sure enough:

Here we can see that the snapshot reserved space is insufficient for the backup to run a storage snapshot. The Equallogic deletes it because of it’s policy and that’s why Windows complains it disappeared unexpectedly.

Conclusion:

You need to either extend the snapshot reserve on the san or run backup without storage snapshotting.

How to configure 3CX with Topex Mobilink IP Gateway

EDIT: 3CX has its own guide since writing this one, find it here: http://www.3cx.com/blog/voip-howto/topex-gsm-gateway/ , as you can see they used some of my post :)
Here’s a how-to on configuring 3CX to use the Topex Mobilink GSM Gateway.
The Mobilink is an inexpensive and robust GSM/UMTS Gateway, but onfortunately there is almost no information regarding it’s setup . And as always with these devices, configurtion can be a pain. So i’ll provide you a step-by-step with screenshots.
This is the Mobilink, complete with Antenna with a long cord, so you can place it where needed.

First off, insert a simcard in the mobilink.
You can open the simtray by pressing the small yellow button with a pen.


Then connect it to your network, the default IP address is: https://192.168.173.1
Click on administration in the left pane, you’ll be prompted to log in.

Default username: admin
Default Password: 99admin11

When you login to the webpage, you’ll see that the WI is not too intuitive, but hey, the device costs less then a smartphone… What do you expect:)

If you have a pincode on the sim, you need to enter that in the Mobilink.
click mobile in the left pane –> settings –> more
here you can enter the pin.

Next we best change the network settings to fit your needs.
Click network in the left pane –> IP Settings –> correct them and save.

Now click the “commit” button on the left and let the device reboot.
You can now access the device on the entered IP address.

It’s best to see if there’s mobile connection now
Mobile –> status

Next you need to configure the incoming calls.
Go to Call controll –> Access IN –> enter your pbx IP here.

Now for Incoming mobile calls:
Call control –> Incoming Calls –> Edit –> More –> make sure mode is set to “trunk” and you are using “target” mode. Enter the local PBX extension where incoming calls should be connected to in the “target” field.
Leave all the rest default.

Now configure outgoing calls:
Call control –> Outgoing Calls –> Enable (that’s all for defaults)

Next you need to tell the Mobilink where your PBX is:
Call Controll –> Settings –> here you can enter the PBX IP

Now click Commit to save everything and reboot the device.
That’s it, the Mobilink is ready for action. Now for the PBX.

First off, we need to configure the Mobilink as PSTN Gateway, so NOT as trunk for outgoing.

In the 3cx management console go to pstn devices –> add gateway –> choose generic –> enter the name for the gateway –> Next

Enter the IP of the Mobilink and keep the rest as shown in the screen. –> Next

In the overview choose which inbound extensions will be called when there is an incoming call… but this doens’t matter, because the Mobilink invites the target you specify. –> Next

Now you have the outgoing PSTN device ready.

Create an outbound rule stating that phonecalls starting with the celular prefix of your country should be routed to the pstn gateway(mobilink)

Now we need to configure incoming calls from the Mobilink to the 3CX PBX.

Open the Voip providers tab in 3CX Managament console –> Add voip provider –> Generic Sip Trunk –> Next

Enter the IP of the Mobilink–> Next

In the next screen you’ll need to enter the external number (doesn’t matter what you enter here) and an auth. ID, doesn’t matter either. –> Next

Skip the incoming and outgoing rules and finish the config.

Now open the Voip provider(Mobilink) you just made by double clicking it and go to the “Source ID” tab. –> Check the thick that says “Source identification by DID”
–> click “Add Mask” –> enter * as mask –> Apply.

Ok, we’re done, you should be ready to make phonecalls in and out using the Mobilink GSM Gateway with 3cx. If not leave a message and I’ll see if I can help you.

How to convert a Cisco LAP to AP

Today I’ll be showing you a step by step on converting a Cisco Lightweight Access Point
to a standalone version. In this tutorial I’ll be using a “LAP-1041N-E-K9″ but other devices will work as well and in the same way.

The LAP is designed to work with a Wireless Controller Unit, and therefor cannot be managed from a webinterface as others can. But luckily you can convert this pretty easy!

This is the 1141n I’ll be working with:

What you need to perform the upgrade:
-A cisco (L)AP
-A Console cable for the AP(optional)
-An ethernet Cable
-A pc/laptop with serial and ethernet port(serial is optional)
-The firmware to convert the AP(get it from cisco site here)
[NO I can't provide the firmware , sorry!]
-A TFTP Server (I recommend Solwarwinds)

To get started install the tftp server on your pc/laptop and disable ALL firewalls.
Place the downloaded firmware (c1140-k9w7-tar.124-25d.JA.tar) in my case in the root of the tftp server. In case of Solarwinds this would be : “C:\TFTP-Root” or whatever you defined as root during install.

Rename the FW file to “c1140-k9w7-tar.default” obviously keep the correct name for your product. This filename is STRICTLY for the 1140 series.

Now make sure the TFTP Server is started and running.

Setup your pc with a static ip on the Ethernet connection “10.0.0.2″ (restart the tftp server if needed)
The AP will assign itself with 10.0.0.1 in safe/debug mode.

Connect the AP directly to the pc using ethernet cable.

Now disconnect the power and press the mode button, keep pressed while reconnecting power/POE. The LED will start flashing blue first and then go to red/amber after 20-30 seconds. Now release the mode button.

(I messed up in this picture, the ethernet should be connected to the Ethernet, not console but i’m too lazy to redo the picture :) )

Now go and check your TFTP Server, you will see a connection from 10.0.0.1 downloading the firmware. During this the LED will keep blinking green.

After the upgrade is complete the LED will stay solid green. Now you can reconnect the AP to your Lan and it will receive a DHCP address, use your prefered scanner to find the AP.
You could also connect the AP to a pc using serial/console and configure it this way if you’re feeling adventerous.(set the transfer rate to 9400)

You can now succesfully login to the webconsole. You now have a standalone AP !

Again , I cannot provide the FW sice Cisco will send me angry letters if I do. :(

How to import PST files in Exchange 2010

Turns out the way to import psts in Exchange 2010 SP1 has changed yet again.
In 2010 you were able to import mailboxen from the EMC, and in 2007 you would do it from another server/client which needed to be x86 and have the exchange management tools installed…
But to be honest i’m glad that’s no longer required.

So down to business:

To be able to import the psts, you  first need the apropriate role memberships/permissions.
To hand out these permissions open the EMS(note that you must have the “organization administration” role/permission)

Issue the following command:

New-ManagementRoleAssignment –Role “Mailbox Import Export” –User <your account>



Then close the shell and restart it, this is needed to enforce your permissions.
Now you are ready to import the psts command is as follows:

New-MailboxImportRequest -Mailbox mailboxname -FilePath \\server\share\file.pst

(please note that it is REQUIRED to use a unc path, this can be \\localservername in case the psts are stored locally. Also it MUST be in a share, so something like c:\folder\psts will not work.

After you completed the command, your request will be queued and progressed, to view this progress you can issue:

Get-MailboxImportRequest

 
Unfortunately there is no such thing as % process or something…


If the import fails, it’s probably because there is a corrupt message(s) in the pst (check event log to verify)
Should this be the case you can add an extra argument allowing corrupt items to be skipped in the import process.

to do so enter

New-MailboxImportRequest -Mailbox mailboxname -FilePath \\server\share\file.pst -BadItemLimit <number of items>

You can import all the mailboxes at the same time, they will be processed one by one.

That’s it you’re done.