fiza

At the moment we are looking at a new MAT wide (3 Schools) VoIP system to be implemented in a few months time once we have chosen a supplier. Problem is that 1 of the Schools needs to have a system in place by 31st March as their current contracts expires then. I was hoping that I could set up a free 3CX onsite solution temporarily until a supplier is chosen later down the line. I would use Orbtalk for SIP trunks. The only issue would be that I would need to port the main School number over so that I could use it with 3CX/Orbtalk. I would then need to port it again to the chosen supplier later on. Does anyone know how long it takes to get numbers ported?

Same!! I see; Minecraft: Education Edition Device Promotion Shape the future If you go into 'Support' and try to raise a support ticket you get an "Access Denied" error!!!!

Just got the same email over the weekend. Occasionally staff want to buy Office Pro for home use, we dont have 0365 running. When I log into the new site it tells me we are not eligible for HUP even though I can see it as active in the VLSC site. Not sure where to go from there!!

I can't set anything in DHCP for phones as we have another VLAN that contains a couple of IP phones for an internal comms system to connect a workshop back to an office. If I set DHCP option 132 then this would affect the existing internal IP phones.

That's how I had it configured originally. That link is for Avaya phones, I am using Yealink. I don't think I need to change my DHCP options as the setup does work, just no through the HP 2848.

untagged on vlan 54 and the phone picks up the correct IP. Problem is that I need these to work with passthru for the computers as some rooms only have 1 network point which is currently used for the computer.

Will give that a go and let you know.

In our Secondary School we have vlans setup but now we are going to introduce VoIP phones. For testing I have a new Aruba 2540 switch and an existing HP procurve 2848 switch. The core is procurve 5412zl. I have added vlan 54 on the core with an IP helper address attached. I have create a DHCP scope for the new vlan.. I have configured the Aruba 2540 for vlan 54. If I connect an IP phone to a vlan 54 tagged port then the phone connects and picks up an IP in the correct vlan. As far as I can see I have the exact same set up on the 2848 but when I plug in a phone to a vlan 54 tagged port it picks up an IP in the data vlan. I read somewhere that the HP 2848 does not support lldp-med which would allow the phone to be recognised as a phone and put on the correct vlan. Does anyone know if this is true and if so how can I get the switch to recognise that an IP phone is connected so that it gets directed to the correct vlan? edit : On further investigation the switch does support lldp so I dont understand why the VLAN will not work.

What you could do is ask some of your more trusted Alumni to post reviews. This will push down the negative reviews.

We used iTS https://www.its-group.com/products/detail/papercut Support is good.

@talksr - any reason why your lease time is so short?

Still get the animation!!!

Thanks. will give that a go now.

@Arthur - Can't find that step Only using MDT/WDS here not SCCM.

I didnt manage to fit this in earlier but I am now going back to it to tidy up the Reference Image. Where abouts in the Task Sequence should I add this as a Run Command Line task?

Just found these articles which exonerate those KBs. https://support.microsoft.com/en-us/help/4480960/windows-server-2008-kb4480960 https://support.microsoft.com/en-us/help/4487266/activation-failures-and-not-genuine-notifications-on-vl-win-7-kms-clie Just trying to remove KB971033 from one affected machine to see if it resolves the issue.

I rejected KB4480970 following @Arthur Thread. I will now check KB4480960 as this may have gone out to computers last night.

Yes windows 7 but we didnt use MAK keys. On VAMT it shows as KMS Strangely when looking at VAMT more closely some of the info doesnt make sense. "The Licence Status last Refreshed" on some machines is way out of date (2017!!). I thought machines had to talk back to KMS every 180 days?

If I use VAMT to activate then I get a message to say "successfully activated" but the expiration date is the date and time I ran the command.

A few of our computers have suddenly started showing "non-genuine". We have had a KMS server for a while now and all was running fine. When we try to activate them with slmgr /ato we get the message " Error Windows is running within the non-genuine notification period" Does anyone know why this is happening and how we can fix it please?

Having the GPOs under the domain OU means the GPOs apply to everything underneath unless the individual security filtering of each GPO has been altered. I put GPOs at the the level they need to be applied. For us the only GPO directly under the domain is 'Default Domain policy'. All others are further down depending on where they need to be applied.

Just declined KB4480970 on our WSUS. Thanks for the heads-up @Arthur

@JohnJackson look forward to the announcement. Will be coming to BETT on the Friday.

Count me in