Author Archive


On-premise Exchange 2010 headaches

by on Sep.01, 2019, under Code, Posts

If you’ve worked in IT and have inherited other systems and networks to manage, you can definitely relate to having to work with situations that are less than ideal. Best practices can’t always be followed due to various reasons. (One main reason seems to be money related.) I am currently working with a client that has on-premise servers that are all bare metal and under-specced. We are in the process gathering information on their current setup and plan to decommission and consolidate their on-premise servers, and push them to use Office 365 instead.

I hope this post helps someone because I was having next to no luck being able to access the Exchange Management Shell. Oddly, the GUI tool worked fine, but I wanted to run powershell scripts to generate reports on the current configuration of the said Exchange server. Clicking on the powershell management shell for Exchange icon would result in:

I troubleshooted all the suggested steps suggested in the error output and everything appeared to check out fine. I then just tried using a standard powershell prompt to try to authenticate to the local exchange powershell, and started getting errors like:

[ExchServer] Connecting to remote server failed with the following error message : The WinRM client received an HTTP status code of 403 from the remote WS-Management service. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc eption + FullyQualifiedErrorId : PSSessionOpenFailed

I found it curious that I was starting to get different error messages and felt like I was starting to get closer to being able to authenticate. What ended up working for me was to issue this command:

$session = new-pssession -configurationName Microsoft.Exchange -connectionuri http://change.me.local/PowerShell/ -Authentication Kerberos -credential $credential 

You are then prompted with a gui logon prompt. Make sure to use Domain\UserName in the username field then use the proper password. Lo and behold, no errors were given and it looks like I was authenticated! To import the exchange powershell modules, issue this command:

Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010;

Again, I really hope this helps save someone a headache and time. As for the root of what’s causing the powershell management shell for Exchange icon shortcut to fail, I’m not clear. So at this point this is just a workaround.

Leave a Comment :, , , , , , , , , , , , , , , , , , more...

Download ESXI 6.7.0 (2019) without registration

by on Aug.07, 2019, under Posts

https://drive.google.com/open?id=1_jOr1QZqMhWLgadW_x7SLSwTw26N6BOj

md5sum:

a87ae18fdeb29c19a8b0c064a81498dc

VMware-VMvisor-Installer-6.7.0.update02-13006603.x86_64.iso

sha256sum:

73950afff2637470b9d347847b2f21cad5a6992becd8c14324668ac6a6ee0f3f

VMware-VMvisor-Installer-6.7.0.update02-13006603.x86_64.iso

 

Leave a Comment :, , , , , more...

iDRAC config reset/configure

by on Jul.29, 2019, under Posts

For those of you who have to work remotely with Dell servers that have active iDRAC interfaces that are either not configured or their configuration isn’t documented, I’ve discovered a useful tool that is written for Linux but works on ESXI as well:

ipmitool – sha1sum 3244c3cee98ef3168193d1a26dca7dfcc732e459

https://drive.google.com/open?id=0BxZG1yRxL_q4TWtURHp1bU84eGFCazlHaWJjcDlfTWN5NUZr

ipmitool-1.8.15-1.vib – sha1sum 3cecaeec586fe06b5ace383a6acf4703fb143a08

https://drive.google.com/open?id=0BxZG1yRxL_q4UE95dTdGaHY0R3RhempnNmFzOUhBX3NVT2dn

With ssh enabled on your ESXI host, you can sftp one of these files to the host and use them to setup iDRAC or reset the admin/root user password.

Virustotal.com results:

https://bit.ly/2LMXQ7m

https://bit.ly/2YazScF

 

 

Leave a Comment :, , , , , , more...


Looking for something?

Use the form below to search the site:

Still not finding what you're looking for? Drop a comment on a post or contact us so we can take care of it!