Here they are, why I forget them all the time is beyond me.
Ctrl + T - opens new PowerShell session in new tab.
Ctrl + Space - runs intellisense against typed text
Ctrl + J - allows to insert predefined code to your script
Ctrl + R - shows/hides script pane (maximizes console view)
Ctrl + I - goes t othe script pane
Ctrl +D - goes to console pane
Ctrl + G - Go to line
F8 - executes one line on cursor position
F5 - executes whole script
Tuesday, 7 July 2015
Friday, 19 June 2015
Flex System x240 M5 PXE not booting
Hello, today I stumbled upon another problem. x240 M5 compute node did't start from PXE.
On pxe server I had tftp error:
tftp: client does not accept options
Problem wasn't on PXE server side, it was compute node configuration issue, more precisely - NIC config. So to resolve it one has to do following:
1. Log in to server's IMM (you can't do it from chassis CMM, it needs to be done from IMM) and go to Server Management --> Adapters.
2. Next, select you ethernet adapter. In my case it is Flex System EN4172 2 port 10 Gbit Ethernet Adapter
3. Go to configuration tab and under "MBA Configuration Menu" change "Legacy Boot protocol" from NONE to PXE.
4. Reboot the node, it should now boot from PXE if you have legacy mode enabled*.
(maybe it'll work with UEFI also, but didn't veriy it)
Update: I checked and it doesn't work with UEFI...
On pxe server I had tftp error:
tftp: client does not accept options
Problem wasn't on PXE server side, it was compute node configuration issue, more precisely - NIC config. So to resolve it one has to do following:
1. Log in to server's IMM (you can't do it from chassis CMM, it needs to be done from IMM) and go to Server Management --> Adapters.
2. Next, select you ethernet adapter. In my case it is Flex System EN4172 2 port 10 Gbit Ethernet Adapter
3. Go to configuration tab and under "MBA Configuration Menu" change "Legacy Boot protocol" from NONE to PXE.
(maybe it'll work with UEFI also, but didn't veriy it)
Update: I checked and it doesn't work with UEFI...
Tuesday, 3 March 2015
Windows 8.1/Server 2012 (R2) classic Start Menu
Windows 8.1/Server 2012(R2) has some sort of classic Start Menu built-in.
Well, it's not a GUI thing, it's just a folder with all standard shortcuts, similar to "All Programs" menu in Windows 7.
How to get it?
1. Right click your taskbar and Toolbars -> New toolbar
2. In Select Folder windows nawigate to C:\ProgramData\Microsoft\Windows\Start Menu\Programs and click "Select Folder"
That's it! Now you have "Start Menu" on your taskbar.
Well, it's not a GUI thing, it's just a folder with all standard shortcuts, similar to "All Programs" menu in Windows 7.
How to get it?
1. Right click your taskbar and Toolbars -> New toolbar
2. In Select Folder windows nawigate to C:\ProgramData\Microsoft\Windows\Start Menu\Programs and click "Select Folder"
That's it! Now you have "Start Menu" on your taskbar.
Sunday, 1 February 2015
How to configure site exceptions in java portable
So, scenario is as following: you want to run remote console or other java app from customer's server without installing Firefox and Java. You cannot disable high security settings in IE.
So you'll probably go with portable version of FF/Java. Cool, but latest java portable is really pain in the bottom, when dealing with outdated or self signed certs.
For me, "Application blocked by security" errors were caused by expired certs.
Normally you'd go to Control Panel opened Java settings and in security tab add there website as an exception. But there's no java applet, because we are using portable version.
We must modify/create exception.sites file to be able to use our Java app:
1. Go to <your user profile>\AppData\LocalLow\Sun\Java\Deployment\security (For some strange reason, despite Java portability, this folder is created in user profile)
2. Modify/create exception.sites file and add there your website starting from "http://" or "https://"
So, for example if your user is Tom it would be:
c:\Users\Tom\AppData\LocalLow\Sun\Java\Deployment\security\exception.sites
And file content looks like this:
http://192.168.10.200
https://192.168.30.20
etc...
Now app should start without problems.
Update:
This method will also work in normal, installed java, if for some reason you don't have java applet in control panel.
If still doesn't work, try commenting (put # in front) line
jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024
in c:\Program Files (x86)\java\<your version>\lib\security\java.version file.
This line in more by the end of file.
So you'll probably go with portable version of FF/Java. Cool, but latest java portable is really pain in the bottom, when dealing with outdated or self signed certs.
For me, "Application blocked by security" errors were caused by expired certs.
Normally you'd go to Control Panel opened Java settings and in security tab add there website as an exception. But there's no java applet, because we are using portable version.
We must modify/create exception.sites file to be able to use our Java app:
1. Go to <your user profile>\AppData\LocalLow\Sun\Java\Deployment\security (For some strange reason, despite Java portability, this folder is created in user profile)
2. Modify/create exception.sites file and add there your website starting from "http://" or "https://"
So, for example if your user is Tom it would be:
c:\Users\Tom\AppData\LocalLow\Sun\Java\Deployment\security\exception.sites
And file content looks like this:
http://192.168.10.200
https://192.168.30.20
etc...
Now app should start without problems.
Update:
This method will also work in normal, installed java, if for some reason you don't have java applet in control panel.
If still doesn't work, try commenting (put # in front) line
jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024
in c:\Program Files (x86)\java\<your version>\lib\security\java.version file.
This line in more by the end of file.
Thursday, 9 October 2014
IBM BladeCenter Qlogic HBA and Brocade modules quirks
This blog post is more for my future reference, but if anyone find it helpfull, cool then :)
Recently, I came across old IBM BladeCenter H chassis and new HS23 blades and IBM Storvize v7000 storage.
Chassis had Brocade 8gig SAN 20 port modules installed. All with old, 2010 firmware....
OK, time for some firmware update joy:
- BladeCenter H updated to BPET66K -good
- SAN switches updated to 7.0.2d6 OK (latest available/supported on IBM FixCentral?) -looks good!
- LAN switches updated to 5.3.5 -fine
- blades updated to TKE140YUS (FW/BIOS), DSYTD8G (Diagnostics), 1AOO64N (mgmt processor) -nice!
- v7000 updated nicely to latest 7.3.06 - great!
Additionally, IBM UpdateExpress DVD updated other parts of blades (mentioned HBA's and other stuff). - fine for me.
I THOUGHT IT DID...
Anyway, work continues - connected the cables, everything should work. But it doesn't. I don't have no light between SAN switch and v7000.
What?
Ok, typical troubleshooting:
Cables are fine.
Zoning is not configured yet, but upstream to other switches works great.
External ports are enabled in AMM.
I did other crazy stuff, disabled ports, switches, changing port speed, etc - still to no avail.
But then my guru said: check fillword parameter. Et voila, changing fillword parameter from 1 to 3 worked like a charm :)
Here's IBM link.
I thought all my problems went away, God, I was so wrong...
Zoning went fine, host were added to v7000, all should be good. But it came out that 2 of 3 of Windows Server 2012 R2 blades reported "Loop down" on one of ports. Second port was fine, so LUNs were accessible, but no redundancy. Obviously, v7000 reported those ports as "inactive".
So digging started:
- ports status on switches? Check!
- cables? Check!
- latest drivers? Check!
- latest firmware? Che... wait, something wrong is going on here - it seems that 2 of those servers have different FW versions, despite running successfully exactly the same UpdateExpress DVD!
Working server had following versions:
Running FW ver: 7.01.00
FW preload table: 2.4.0
FW Serdes Table: 1.0
BIOS ver: 2.14
FCODE ver: 3.20
EFI ver: 2.51
After I updated servers with correct versions (by using single file, qlgc_fw_fc_8g-f70100-b214-e251_windows_32-64.exe, which btw was on UpdateExpress DVD, all problems went away.
(One more reset of switch ports helped a little :) )
Oh, and SDDDSM_x64_2435-3_140627 is installed also.
TL;DR: pay attention to fillword parameters if you are implementing IBM Storvize v7000. Double check installed firmware versions!
uh, it took me too much time..
Recently, I came across old IBM BladeCenter H chassis and new HS23 blades and IBM Storvize v7000 storage.
Chassis had Brocade 8gig SAN 20 port modules installed. All with old, 2010 firmware....
OK, time for some firmware update joy:
- BladeCenter H updated to BPET66K -good
- SAN switches updated to 7.0.2d6 OK (latest available/supported on IBM FixCentral?) -looks good!
- LAN switches updated to 5.3.5 -fine
- blades updated to TKE140YUS (FW/BIOS), DSYTD8G (Diagnostics), 1AOO64N (mgmt processor) -nice!
- v7000 updated nicely to latest 7.3.06 - great!
Additionally, IBM UpdateExpress DVD updated other parts of blades (mentioned HBA's and other stuff). - fine for me.
I THOUGHT IT DID...
Anyway, work continues - connected the cables, everything should work. But it doesn't. I don't have no light between SAN switch and v7000.
What?
Ok, typical troubleshooting:
Cables are fine.
Zoning is not configured yet, but upstream to other switches works great.
External ports are enabled in AMM.
I did other crazy stuff, disabled ports, switches, changing port speed, etc - still to no avail.
But then my guru said: check fillword parameter. Et voila, changing fillword parameter from 1 to 3 worked like a charm :)
Here's IBM link.
I thought all my problems went away, God, I was so wrong...
Zoning went fine, host were added to v7000, all should be good. But it came out that 2 of 3 of Windows Server 2012 R2 blades reported "Loop down" on one of ports. Second port was fine, so LUNs were accessible, but no redundancy. Obviously, v7000 reported those ports as "inactive".
So digging started:
- ports status on switches? Check!
- cables? Check!
- latest drivers? Check!
- latest firmware? Che... wait, something wrong is going on here - it seems that 2 of those servers have different FW versions, despite running successfully exactly the same UpdateExpress DVD!
Working server had following versions:
Running FW ver: 7.01.00
FW preload table: 2.4.0
FW Serdes Table: 1.0
BIOS ver: 2.14
FCODE ver: 3.20
EFI ver: 2.51
After I updated servers with correct versions (by using single file, qlgc_fw_fc_8g-f70100-b214-e251_windows_32-64.exe, which btw was on UpdateExpress DVD, all problems went away.
(One more reset of switch ports helped a little :) )
Oh, and SDDDSM_x64_2435-3_140627 is installed also.
TL;DR: pay attention to fillword parameters if you are implementing IBM Storvize v7000. Double check installed firmware versions!
uh, it took me too much time..
Wednesday, 23 April 2014
Paged and nonpaged pool memory leaks... caused by zombies!
Ugh, it's been over a year since I posted here... hope I'll make updates more frequently...
Anyway, recently I struggled with pinpointing cause of memory leak on some Windows Serve r2008 R2.
This leak was quite rare, because it wasn't caused by working applications, instead, due to some driver bug, system wasn't able to release all memory from closed proccesses (20K to be precise) and this eventually caused all physical memory to fill up... and crash the server.
It looked like this in RAMmap:
Thanks to this post I was able to find problematic driver. And it was indeed, Alladin HASP USB dongle driver.
So, lesson learned: if you think you have memory leaks, go check it with RAMmap also. Proccess explorer or similar tools can show you leaking active app.
And just for reference: fltmc command can help find active filter drivers which may cause memory leaks.
Anyway, recently I struggled with pinpointing cause of memory leak on some Windows Serve r2008 R2.
This leak was quite rare, because it wasn't caused by working applications, instead, due to some driver bug, system wasn't able to release all memory from closed proccesses (20K to be precise) and this eventually caused all physical memory to fill up... and crash the server.
It looked like this in RAMmap:
Thanks to this post I was able to find problematic driver. And it was indeed, Alladin HASP USB dongle driver.
So, lesson learned: if you think you have memory leaks, go check it with RAMmap also. Proccess explorer or similar tools can show you leaking active app.
And just for reference: fltmc command can help find active filter drivers which may cause memory leaks.
Tuesday, 2 April 2013
Those pesky 0x8024402c WSUS errors...
If you administer WSUS you probably had this 0x8024402cerror in WindowsUpdate.log already, right?
So, let's check together:
- no WinHTTP proxy (here)? Check!
- IIS is working fine on WSUS server? Check!
- DNS resolves servername? Check!
- GPO's are flowing nicely and you have your WSUS server defined under WUserver and WUStatusServer in HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate? Check!
Still having this error? Go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU and check if you have UseWUServer=1 DWORD entry. I didn't have it and it was the reason of problems, despite that GPO's were ok.
For reference I suggest this technet article.
So, let's check together:
- no WinHTTP proxy (here)? Check!
- IIS is working fine on WSUS server? Check!
- DNS resolves servername? Check!
- GPO's are flowing nicely and you have your WSUS server defined under WUserver and WUStatusServer in HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate? Check!
Still having this error? Go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU and check if you have UseWUServer=1 DWORD entry. I didn't have it and it was the reason of problems, despite that GPO's were ok.
For reference I suggest this technet article.
Subscribe to:
Posts (Atom)



