Comment Re:WMI (Score 1) 427
Powershell does a great job of bringing WMI to the shell.
Get-WMIObject WIN32_BIOS
Not only can you query with wmi, but get access to the objects to call various WMI functions.
Powershell does a great job of bringing WMI to the shell.
Get-WMIObject WIN32_BIOS
Not only can you query with wmi, but get access to the objects to call various WMI functions.
There is a lot of power in PowerShell remoting now and its easier than ever to use now.
Get-Content
This works great for simple stuff. The commands in the -ScriptBlock are ran on the target computer. The -AsJob is not needed, but it basically multi threads the command. Running it on every computer at the same time instead of one at a time. You have to use get-job and related commands to check up on them, but its worth it when I want to run a command on hundreds of computers that may or may not be online.
I'm sure you may have figured out most of that but may be struggling with network access in remote shells or need different credentials other than your own. You need to enable CredSSP on your remote computers for passthrough authentication (for network access in remote shells). You can enable this in AD for Win7 computers but its a bit more work for WinXP. Using CredSSP requires you to pass credentials. Here is an example that pulls those together.
$Cred = Get-Credential
Get-Content
In this Get-Credential will prompt for the username password. I changed the ScriptBlock to run a program off a network share. This would have failed in the first example. One other thing about using CredSSP, it needs a FQDN of the computer. I am not sure if this is any simpler than psexec. I remember using it for automation years ago but have forgotten all about it. I do find all of this easy to remember though.
I find myself running commands like this all the time now. Combining this with Get-QADComputer from quest to get computer accounts and having wake on lan scriptable will give you tons of power. I just wanted to share with you and everyone else how cool the remoting features of PowerShell can be.
They need to just focus on smartphone integration. The people craving these features are the early adopters that already have a smartphone. You can get navigation and internet radio with that already.
Our privacy policy:
You have no expectation of privacy. We will collect any and all information you or your computer is willing to give us and do whatever we want with that information. Use of this site is entirely optional. Use at your own risk.
All my "TV" watching is now from streamed Netflix or Hulu. I use it more like a radio, but it is on all the time.
it was only a matter of time.
Check the name on the cert. if it is self signed, then you just have to deal with it. But if it is root signed, look at the site name. If you can find a way to use that site address to access the device then you will not get prompted.
My home router has a valid cert, but I would use the ip address and get prompted every time. I ended up making an entry in my host file for "linksys" at that address. Now when I go to https://linksys/ everything is ok.
At the end of the day, remember the whole reason these devices use SSL is not so you can verify the connection. They use it to encrypt the connection. It is so much better to use SSL instead of plain text, even though the cert is not root signed.
If you make your microsoft certificate authority the domain authority, I think that it will automatically distribute the root cert to every domain joined computer at the next computer policy refresh.
Not only that, but there is a section of group policy just for certificates. It is very easy to work with (if you are using a Microsoft authority).
The cost is that of another server (or a few servers for a large organisation).
I have 100% replaced my cable TV. I watch a lot of TV. Well, I have the TV on a lot if I am watching it or not. I use it kind of like a radio.
The programming is also perfect for kids. They have just a few shows that they watch over and over again, the icons are big enough that they can tell what the show is.
I am watching a lot of old shows that I forgot about. Catching an old series from episode 1 forward is great.
I also have Hulu for the more current shows.
This is wonderful and cheap. I pay less than 10$ for all my TV entertainment now (on top of my internet connection). If you look at it that way, for people that drop Cable TV and Dish TV, if they had to pay an additional 10$-40$ for a better internet connection or more bandwidth, they would still be saving money each month. I am paying about 60$ a month less than I was with Dish TV.
I expect that at some point things will balance back out again. I don't want the fact that I am watching a lot of Netflix to impact my internet service, but I expect that it will at some point.
Use a switched network
This is a packet sniffer. If you are on a switched network, the degree of difficulty to pull this off is much greater. it is not a solution because of other tricks like arp poisoning.
This is nothing new, but it is good publicity to remind people how important SSL is. This addon did not change anything except now more script kiddies have access to another tool.
Verifying that every client received the same message is fairly easy. You can just collect the logs and compare. A good damage meter does more than that.
With that said, if they would have built a damage meter then the logs would be more accurate and the resulting damage meter would be more accurate.
The early damage mods parsed the combat log as text. So every mob that had the same name was the same mob. single pulls were fine, but double pulls of the same mob was confusing. Then pets were an issue. If 2 people had a wolf named wolf or god help you if someone named the pet after someone else in the raid. Blizzard saw this issue and revamped the logs so there were ID numbers for mobs.
I wrote a damage meter once for another game (when people told me it was impossible to do in AOC). Text parsing natural language combat logs is not fun but it is doable.
Even though no information has been released yet, I would expect to see something in the next 2 years. That would put Windows 7 at 3 years old. If we don't see a release, we should be seeing some betas by then. They will not wait 5 years again like they did from XP to Vista and the Vista to Win 7 timeline was 3 years.
"Don't try to outweird me, three-eyes. I get stranger things than you free with my breakfast cereal." - Zaphod Beeblebrox in "Hithiker's Guide to the Galaxy"