Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 



ISOHaven

Member
  • Content count

    180
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

2 Neutral

About ISOHaven

Profile Information

  • OS
    none specified
  1. You do not need to input all X's. The problem you guys are having is that you are trying to "skip" it. That's not possible. You need to let the product key process run. When it runs it will pick up the key in the BIOS. Specifing for it to never run or to show errors will cause it to error out. Just leave the Key field blank and tell it to ALWAYS show. If there's a BIOS key to be found you will never see the CD Key window, it will in fact proceed unattended. <UserData> <ProductKey> <Key></Key> <WillShowUI>Always</WillShowUI> </ProductKey> <AcceptEula>true</AcceptEula> </UserData> Removing ProductKey altogether as the OP has done will also throw out an error.
  2. Start Is Back - 2.1 release

    It's working fine for me.
  3. Start Is Back - 2.1 release

    No glass that I know about.
  4. Start Is Back - 2.1 release

    Unfortunately I highly doubt many "corporations" will go with this. I tried when we were all Win8 and they just wouldn't bite with 8.1 right around corner which solved most no menu problems. Then once they saw the new start menu in Win9 that pretty much killed it completely.
  5. Start Is Back - 2.1 release

    That's all that really matters!
  6. Start Is Back - 2.1 release

    I registered. Found out they had nothing but NT4.0 classes. NT4.0 was on it's way out the door then realized my diploma would be something that actually expired. I wasn't about to pay 40+ grand for that (today around 100k+). Now I have well over 10 years experience under my belt which is worth way more than a diploma in this field. Experience AND a diploma....I would hate those people except they're STILL paying off their student loans. Poor bastards....oh....now I get it. Yeah, they need a freebie handout.
  7. Start Is Back - 2.1 release

    I never went to college. Now I feel discriminated against!
  8. Start Is Back - 2.1 release

    Woot! Congrats!!!! Happy Gobble Day!
  9. Start Is Back - 2.1 release

    Thanks! I've got a ton of catching up to do but as soon as I can I'll load an 8.1 VM and give this a thorough run in my domain environment.
  10. Start Is Back - 2.1 release

    Hey everyone!!! Been a long time! I wont bore anyone with the details as to why I disppeared. How you been Tihiy? Anywho, came across this error message every time I go to add/remove policy templates: Resource '$(string.SUPPORTED_Win8Only)' referenced in attribute displayName could not be found. Line 11, column 89 Looks to be refering to this line: <definition name="SUPPORTED_Win8Only" displayName="$(string.SUPPORTED_Win8Only)" /> EDIT: Bleh, never fails! Always find an answer after posting. Somehow the ADML file became corrupt. After fixing it the problem went away.
  11. Start Is Back - 2.1 release

    At first I was like...WTF?
  12. Start Is Back - 2.1 release

    I think that was just a license question??? At any rate, June 26th is just around the corner!
  13. Start Is Back - 2.1 release

    I've added legacy userpic loading (if domain joined only). The rest of Windows 8 does not pick it though; i guess there should be some new tool for setting picture via .accountpicture-ms. If there is I've not found it yet. Why the FRACK MS hasn't added domain support to the (temp) local account with domain joins is driving a lot of us in IT absolutely mad. What's weird though is my domain account on all my 2012 servers DO have my admin pic for the login but only when doing RDP....WTF!?!?!?! Get your crap together MS! EDIT: Duh.... Forgot to mention it works now. Picked up the domain user pick with no problems!
  14. Start Is Back - 2.1 release

    It doesn't pick up the user pic. Here's my login code for populating the user pic: $username=$env:username $domain=$env:userdomain $temp=$env:temp $photo = ([ADSISEARCHER]“samaccountname=$($username)”).findone().properties.thumbnailphoto if($photo -eq $null){ $command = “\\DOMAIN\netlogon\pictures\usertile.exe $domain\$username \\DOMAIN\netlogon\pictures\default.jpg” } else { $photo | set-content $temp\$domain+$username.jpg -Encoding byte $command = “\\DOMAIN\netlogon\pictures\usertile.exe $domain\$username $temp\$domain+$username.jpg” } cmd /c $command And here is the source for usertile.exe: using System; using System.Runtime.InteropServices; namespace TilePicture { class Program { [DllImport("shell32.dll", EntryPoint = "#262", CharSet = CharSet.Unicode, PreserveSig = false)] public static extern void SetUserTile(string username, int whatever, string picpath); [STAThread] static void Main(string[] args) { SetUserTile(args[0], 0, args[1]); } } }
  15. Start Is Back - 2.1 release

    Whoa! That's awesome! Outstanding work! User pic will be one of the hardest. If you wind up implementing your own way of adding the pic then it'll break all sorts of network/domain stuff.
×