And it doesn't go ribbit :-)
Friday, September 30, 2011
Thursday, September 29, 2011
Hmmm #Windows8 #IE10 Certificate issues - anyone seen incorrect revoked
I've loaded the laptop (a touchscreen one) with the dev build of Windows 8. So far so good. The highlights have to be
a) it works!
b) it boots in under 20 seconds (and that's with a normal BIOS, not UEFI)
c) it installed in about 15 minutes from a blank disk to a logon screen
However, working from home, I was working with Outlook on the box and got some problems so thought I would hit the OWA site for my email, when I did so, I got this:
That was a bit of a showstopper!
So I've done the usual google thing, nowt.
I've tried the Outlook Anywhere connection - fails.
I then VPN'd into the network, and hit the Exchange CAS server with the local name and logged on fine.
So the certificate is not revoked.
Further supporting evidence is the fact that ActiveSync is still working on the phones, and I can use OWA from the iPad.
So, anyone seen this? Got a fix? The only clue I can think of is that the certificate is for a non-standard name; it's not for www but owa.
Ta, Peter
a) it works!
b) it boots in under 20 seconds (and that's with a normal BIOS, not UEFI)
c) it installed in about 15 minutes from a blank disk to a logon screen
However, working from home, I was working with Outlook on the box and got some problems so thought I would hit the OWA site for my email, when I did so, I got this:
That was a bit of a showstopper!
So I've done the usual google thing, nowt.
I've tried the Outlook Anywhere connection - fails.
I then VPN'd into the network, and hit the Exchange CAS server with the local name and logged on fine.
So the certificate is not revoked.
Further supporting evidence is the fact that ActiveSync is still working on the phones, and I can use OWA from the iPad.
So, anyone seen this? Got a fix? The only clue I can think of is that the certificate is for a non-standard name; it's not for www but owa.
Ta, Peter
#LFMF VMware datastores are case sensitive!
Working in a Microsoft world with only brief forays into Unix and Apple server technologies, I tend to forget some lessons from those alternatives :-)
So, today when working on some PowerShell scripts to copy datastore folders around for backup purposes I was a bit stumped by a copy failing as no object was found. The essential components of the script are:
Add-PSSnapin VMware.VimAutomation.Core
Connect-VIServer -Server FQDN of server or vCentre -Protocol https
$datastore = Get-Datastore Test
New-PSDrive -Location $datastore -Name TT -PSProvider VimDatastore -Root '\'
Copy-DatastoreItem 'TT:\sage\*' 'J:\esx\test\sage'
start-vm -vm 'Sage'
The Add-PSSnapin puts the VMware supplied PowerCLI snapins in place to manage ESX/vCentre architecture
Connect-VIServer does what it says on the tin
New-PSDrive creates a PowerShell drive mapping to the datastore in question so that it can be maipulated., and the Copy-DatastoreItem with those parameters copies the entire folder over (you can recurse through folders and so on if you wish, this is a simple copy)
Can you see the mistake, no I couldn't either!
The script would fail on the copy-datastoreitem command and jump onto the start-vm. Now I know there should be error handling and all that stuff, but this was a quick 1-off to sort something out.
So I browsed teh data store through the vCentre interface, all was there, the target folders were there...
In the end the Unix issue of capitalisation rang a distant echo. The Sage folder on the datastore was precisely that "Sage" not "sage".
Quick edit, and all is running.
Phew!
'scuse the inappropriate word wraps in the code.
So, today when working on some PowerShell scripts to copy datastore folders around for backup purposes I was a bit stumped by a copy failing as no object was found. The essential components of the script are:
Add-PSSnapin VMware.VimAutomation.Core
Connect-VIServer -Server FQDN of server or vCentre -Protocol https
$datastore = Get-Datastore Test
New-PSDrive -Location $datastore -Name TT -PSProvider VimDatastore -Root '\'
Copy-DatastoreItem 'TT:\sage\*' 'J:\esx\test\sage'
start-vm -vm 'Sage'
The Add-PSSnapin puts the VMware supplied PowerCLI snapins in place to manage ESX/vCentre architecture
Connect-VIServer does what it says on the tin
New-PSDrive creates a PowerShell drive mapping to the datastore in question so that it can be maipulated., and the Copy-DatastoreItem with those parameters copies the entire folder over (you can recurse through folders and so on if you wish, this is a simple copy)
Can you see the mistake, no I couldn't either!
The script would fail on the copy-datastoreitem command and jump onto the start-vm. Now I know there should be error handling and all that stuff, but this was a quick 1-off to sort something out.
So I browsed teh data store through the vCentre interface, all was there, the target folders were there...
In the end the Unix issue of capitalisation rang a distant echo. The Sage folder on the datastore was precisely that "Sage" not "sage".
Quick edit, and all is running.
Phew!
'scuse the inappropriate word wraps in the code.
Wednesday, September 28, 2011
Want #Mango #WP7 now? But your network connection is not immediately adjacent to your desk, or awkward to break. #PowerShell
Mango is now available, and there is a cheat that seems to bypass the “wait until Microsoft/Your Carrier” make it available to you. Read more here: http://www.wpcentral.com/force-mango-update-early-through-zune-software
However the trick relies on disconnecting your internet connection within a few seconds. This is fine and dandy if the cable is right by your keyboard, mouse and monitor, but not if it isn’t.
Obviously you can enable/disable the NIC, but Windows 7 (at least here) takes a variable amount of time to perform the disconnect. Factor in UAC asking you for permission to disconnect then you have a bigger timing problem.
So a quick jump to the internet. The following lines of code sort it out.
Firstly, start a PowerShell session (ISE or prompt), but with Run as Administrator rights to avoid issues.
Then use the line:
Get-WmiObject -Class Win32_NetworkAdapter | Format-Table Name, NetEnabled, NetConnectionStatus, DeviceId –auto
This lists all your network connections, (extract below)
Name NetEnabled NetConnectionStatus DeviceId
---- ---------- ------------------- --------
<snipped>
WAN Miniport (Network Monitor) 6
Intel(R) PRO/1000 MT Server Connection True 2 7
<snipped>
Identify the Device ID for your network connection. In this case 7.
The following lines of code needs to run once only in your ISE session
$Nic = Get-WmiObject win32_networkadapter -computerName LocalHost -filter "DeviceId = 7"
Note that the number 7 at the end will need to be changed for your environment.
Then finally –
$Nic.enable()
or
$Nic.disable()
As you wish to switch your NIC on and off.
So, having prepped all that, a quick click on linking on the Zune screen below
Followed by a click on UPDATE, and then immediately run the disable command, and Robert’s your mother’s brother. When you click on the presented choice to download an update – don’t forget to enable your link again.
Note you may need to update teh Zune software, so you'll get a bit of this:
For a bit.Note you may need to update teh Zune software, so you'll get a bit of this:
But then you should see an update offered, something like this.
![]() |
| 7403 offered to user |
![]() |
| 7403 ready to download |
Repeat until you have Mango installed
Enjoy!
Labels:
Backdoor,
HTC,
Mango,
Microsoft,
OrangeUK,
PowerShell,
Problem,
Succeed,
Windows Mobile,
WP7
at
12:25 pm
3
comments
Subscribe to:
Posts (Atom)




