Let me start off by saying “when setting up your PowerShell in a new OS environment, be sure to load your assemblies first otherwise you may not see ANY commands in the command viewer”.
This is just an FYI for anyone who does a “clean” install of Windows 10 and then wants to set up their PowerShell similar to what they had.
I use PowerShell with SQL Server almost exclusively. My environment had a profile, a module of frequently used functions for SQL Server, and a folder with numerous POSH scripts which was included in my path.
After installing Windows 10, I fired up PowerShell ISE and found it to be working perfectly. After adding my module folder to the PsModulePath and adding my scripts folder to the Path, I found I could no longer view ANY commands in the ISE command viewer! Working backwards, I took my scripts library out of the Path and restarted the ISE. Lo and behold, the command viewer now showed the commands again. After adding my scripts folder back to the path, command viewer would not display any commands.
I decided to load my SQL Server assemblies, performed a refresh on command viewer and made some progress. Now an error message popped up regarding an error in one of my scripts (in the path). After correcting several script errors, all available commands now showed up in command viewer.
I restarted PowerShell and the commands were no longer viewable again. I then added the loading of my SQL Assemblies into a profile and after restarting, all commands were once again visible in command viewer.
It would appear that the new PowerShell does some type of error checking for scripts in your path and if the scripts reference assemblies not loaded, it breaks down with regard to Command Viewer.
This is for anyone having a problem installing the print drivers for a Canon Pixma MX870 printer. I have two machines, one is new and came with Windows 10 installed and the other had Windows 10 installed as an upgrade after restoring it to the OEM Windows 7 Home.
The newer downloaded drivers from Canon installed with no problem on the new machine but aborted with an error on the upgraded machine. The error reported was “Canon IJ Driver Installer Has Stopped Working”. After re-downloading, uninstalling, re-installing, restarting, googling, etc. I contacted Canon support. They were very responsive and after several attempts, we finally got the install to complete without error and the printer and software are working great.
The final resolution is listed in this excerpt from a Canon Support email:
- From the Start menu, click Settings, Devices, Printers & Scanners.
- Towards the bottom of the Printers & Scanners area, turn off Let Windows manage my default printer.
- Once this has been done, re-install the drivers again.
You may also have to delete any extra icons of the printer in the Printers & Scanners menu.
Beware of a new default when installing Oracle 11g! This default can raise its ugly head and bite you in the ass! It just happened to me.
The default has to do with enforcing a password expiration when creating a user. I don’t know about you but we generally have applications (Oracle based as well as SQL Server) which rely on user logins specific for that application. These applications also have configurations in which you specify the user login, sometimes in several locations. Users and application managers come and go and along with them the knowledge of application configurations and where they are. Consequently, we do not change application passwords! As soon as you do, applications break and it could take hours or even days to get them working again.
With this in mind, you might seriously think about changing the Oracle 11g default policy as one of your steps immediately after installation. I did not change the policy as I was unaware of it. I had several user logins become disabled duet to expiring passwords. These also included SYSTEM and DBSNMP! Talk about a real PITA!
Here’s how you can change the password policy:
ALTER PROFILE DEFAULT LIMIT
Oh! And by-the-way, if the password does expire, you cannot unexpire it. You are forced to supply a new password even if it is the same as the old one. Unfortunately in my case, the application was installed by a third party and they were not sure of the password.