Ignore the idiot AC who responded to you. Password storage has nothing to do with Kerberos. The two things are related, but orthogonal.
Windows still uses NTLM without a salt in the current versions.
There is a way to encrypt the SAM with a symmetric cipher, which requires that a floppy or USB key must be physically present for the SAM to be accessed. It's not widely used.
Here here.
Anyone who says that recovering passwords is never necessary, since you can just change them, obviously has never done much work in this field.
Dude, seriously. Its nice and all that you like to brag about multiple languages. Good for you.
But do you really know a language if you cannot communicate effectively with it?
Case in point, your post that I'm responding to.
It's fairly badly broken English. I've read worse, but its not good.
For example, how do you get 'too sticked to grammer', and what the hell does that mean? Is it some kind of dom/sub foreplay?
What is a 'juridical' document? Sounds kinky.
And I dont even have a clue what this is supposed to mean:
... when people try to teach grammar not by the error but by playing smarties.
Now there are alot of people who arent native english speakers here on
Bottom line, if you want to be able to be understood, and engage in conversation with people, then slow down a bit and at least try to make your posts intelligible. The couple of your posts I've read on this story are nearly incomprehensible. Strangely enough, the most clear you've been was in your bragging about how many languages you know, so that tells me you can speak clearly in English when you want to.
I think the issue is more the drivers.
If your equipment supports x64, then the drivers are either freshly written for Vista, or have gotten quite a bit of work.
I think a big part of the problem before was that alot of low-end, consumer level equipment shipped with drivers that were minimally modified from XP so that they (just barely) worked. But if the equipment was to support x64, they had to put some real resources into developing the drivers.
This leads to another general rule of thumb for vista: You'll do MUCH better if you buy equipment that is officially supported in x86 or x64. Stuff that is NOT supported in x64 seems to be lower quality, and more shoddy in the drivers.
And since Vista is heavily sensitive to bad drivers
Actually, I think you'll find that in the corporate space, HP has some of the best kit out there.
In corporate-level laptops (ie, things branded Compaq, not the crap you buy in BestBuy), they're absolutely fantastic. Nearly flawless.
In x86 servers, the ProLiant's are also fantastic.
In particular, the high end HP laptops run x64 Vista quite well. Seems like that class of machine is one of the only ones to have quality drivers.
The achilles heel of Vista is drivers. If the drivers have problems, then the whole thing falls over.
As a counter-example to yours, I'm running Vista x64 Business on an HP Compaq 8710w laptop. 2.4C2D, 4GB memory, 7200rpm hdd, and an Nvidia Quadro FX 1600M with 512MB onboard.
This machine shipped from HP as x64 ready, and has been the most flawless laptop I've ever owned. It runs basically until the once a month updates from MS, and I abuse it pretty heavily, running Oracle Enterprise 10g, Eclipse, and Tomcat with a couple big app servers, all a part of normal development. I actually am looking at moving up to 8GB of memory, as the 4 isnt really enough for that kind of use (I have the swappiness set really low).
It literally just keeps going, and keeps going, and keeps going, and never stops. It's also the most reliable Vista machine I've seen in the field, though I think that has more to do with it being a high-end engineering laptop from HP, so the drivers are high quality.
Be careful that many CAD/CAM/CAE apps dont really support 64-bit properly, though I cant speak specifically to SolidWorks. Too many apps in that space have near monopolies, and just never upgrade their software.
1. Group Policy management (the move to admx files has caused numerous backwards compatibility issues)
This is a pretty minor issue.
2. The ever-growing winsxs folder. There is no way to shrink or compress it.
Who cares? If you're trying to rollout Vista on machines with 20GB hard drives, then you made a bad choice to do so. Your equipment isnt ready for Vista, and there's no big rush, so why are you trying to move when you're not ready?
3. Try creating images with default software for imaging workstations due to #2.
I dont understand what #2 had to do with this. Creating images with default software works just fine. The size of the winsxs folder is irrelevant to that task.
4. In-house applications need to be recoded.
This means in-house apps were done wrong in the first place, and need to be fixed. This isnt a Vista problem, this is a lazy/incompetent/badly-managed in-house apps group problem. Thats like blaming your ISP because you have some users that are bottlenecking your internet connection with bittorrent.
5. Minimum requirements for Vista would require a major purchase of machines to be able to run it.
Then dont do it.
6. Activation process fails ~1/3 of the time, even when trying to use an in-house key server.
This is not the normal experience.
7. Random core dumps on Dell Latitude laptop line (have had 8 of them do this), even with the latest drivers and firmware.
Is this on the Dell Latitude E-series? If so, this is about Dell's problem, not Vista. There are BIG hardware problems with some of the E-lines, just do a quick google. It's all over the news.
If you turn off UAC, how do you elevate to an admin account when you need to install new software or change system settings?
Runas doesnt really work right in Vista, so I'm betting that isnt it.
That's not UAC. What you are talking about is the (simple) difference between a user and an administrator. Microsoft has never understood that difference.
And you clearly dont understand the software you're talking about.
Which leads us to the BS that is UAC... even with admin rights you still have to confirm every damned thing you do. It's a horrible stupid kludge. If you don't what people doing "admin" things, don't make them an admin. (it's a tough concept in the windows world.)
If you dont like UAC in that configuration, why not change how UAC behaves? Turn off admin-approval, and change the UAC behavior so it works more like sudo, or like the XP-style runas.
It seems to me like you didnt take 5 minutes to google how to tweak your UAC config from the grandma & grandpa home-user configuration it ships with to a more suitable one for yourself.
The reason Linux has (basically) no virii is not only because of its low market share, but because it's inherently secure, and requires permissions to do system-vital tasks. Unless you're running every application you open with sudo, in which case you're an idiot.
Depends what you mean by 'inherently secure', but if you mean it 'requires permissions to do system-vital tasks', well then every corporate windows version for quite a long time has had this as well.
Depends what your definition of 'virii' is. There is a massive amount of automated attacks going on specifically targeting linux systems on a constant basis. Higher volume than the automated attacks targeting windows vulns in my experience.
Your statements are only applicable if you consider virii things that target desktop applications or consist of social engineering attacks to convince users to run their malware with elevated privileges.
Could you not even be bothered to read the article you linked?
They have ~$25B in cash.
They're selling bonds to generate ~$3.75B in additional cash.
They clearly dont 'need the money', they're just leveraging the credit situation and their own good credit rating. It's no different than someone who borrows against equity against their home at 4.5% and re-invests that into the stock-market to earn 5-10%.
Not to mention the package manager keeps track of EVERY package on your PC (as long as it was installed via the package manager) as well as the core system itself, so updates are a one-click deal.
This is only true if the software you need is open source, packaged by your package manager, and is ported to your distro in a timely manner. I run into a _lot_ of situations where the package managers dont have what I need and I have to out and either compile the stuff myself or download and run some scripted installer.
So yeah, package manager is great for the base commodity desktop apps. But if its not in the package manager, and there's alot thats not, it sucks the big one.
With Windows the Windows updates system only does WINDOWS updates, nothing else. You have to do every application separately, which means a LOT of clicks, with a LOT of different GUI's to interact with to stay updated.
Actually, Microsoft Update updates nearly all Microsoft software. Office packages, development tools, database servers, exchange servers, web servers, utilities, driver packs, etc etc. It doesnt do everything, but on most windows installs it covers a great deal.
This is not to suggest that its perfect and does everything, but your representation of the situation was not accurate.
This is only tru
It goes both ways. I've literally never, in my entire life, been able to get a linux install to work with the wifi on a laptop. Ever. Even on my new hp compaq that has the intel abg card with open source drivers. Even on the 3 laptops before that, all dell before the hp.
And the last few laptops I tried to install linux on, I had to go through a fairly bizarre ritual involving only using the alternative setup disc, editing grub to suppress the splash screen, and then manually downloading nvidia drivers with wget.
I know not everyone runs into that, but the fact that I've run into the exact same set of problems with nvidia and wifi drivers across several different dell latitude generations and a brand spanking new hp compaq is worrisome.
On the flip side, HP ships a handy dandy driver disc that includes 32-bit and 64-bit drivers for both Vista and XP, so its kind of a stacked game.
In XP I had to click "Start" -> "Control Panel" -> "Network Configuration" to start he wizard. Now the freaky part begins. One has to click on several pages that show only some warning text. You need to click on a box to make it disregard disconnected network hardware (WHY? I'm not changing the hardware, just the network address). Enter the computer hardware description and name (WHY? I'm not changing that, just the network address). Type a workgroup name. Tell it if I want to change disk and printer sharing (NO! I just want to change the network address!!!). Another nag screen asking me if I want to create a configuration disk (NO!!!). Then it tells me I need to reboot the computer (WHY? I just want to change the network address...)
Are you just making random things up here?
The way you do it is to right click the network icon in the system tray, choose properties, double click on TCP/IP and then enter your IP.
You seem to have stumbled across some sort of deeply buried 'try to do everything' wizard that I've never even heard of or seen, and that nobody on earth uses.
Of course, your whole scenario was specious. If your machines and your network are setup correctly, the correct way to do that was to plug an ethernet cord into your computer, and you're done. The box gets an IP address from the router. Given that you can get an adequate router/firewall from your ISP for little to nothing, I havent heard of or seen anyone use a computer to share the network since the 1990's.
Love may laugh at locksmiths, but he has a profound respect for money bags. -- Sidney Paternoster, "The Folly of the Wise"
