Find folder “HKEY_LOCAL_MACHINE” double click on itĦ. User Account Control warning may pop up – click “Yes”ĥ. You can edit the registry yourself by doing this:ģ) save the file on your desktop (or anywhere else) as name.reg – “.reg” is important.Ĥ) run the file and press yes on the 2 poppups.ġ. * Update on : How to add permission to a shared folder for Vanessa.įor windows 7 home premium i found this solution to work just fine. * Update on : If your network drive host is a Windows 2000 server, you may need to upgrade it to SP4. Choose Send LM & NTLM responses in Network security: LAN Select the Security Option under Local PoliciesĤ. Open the Administrative Tools in the Control Panel in your Windows 7 (NOT the network drive server)ģ. So i asked the Google teacher and finally found the solution. I cannot map to the network drive! It said the password is not valid! Much much faster than Vista and all XP softwares such as Tortoise SVN, VM Player, DB Visualizer … could run without any problems. My first feeling on Windows 7 is quite good. So i migrated all the stuff to a new computer and try the Windows 7 Professional which HKU provided. $($Record.MachineName, $Record.Status, $UnJoinStatus.ReturnValue, $JoinStatus.Back from Spain! I will summarize my trip a bit later =)Ī few days ago, i found that my office computer was getting slower and slower and it always hanged for a while whenever i did any action on the Windows Explorer.
$JoinStatus = $ObjMachine.JoinDomainOrWorkgroup($DomainName, $Password, $($DomainCred.UserName), $MachineParentOU, 3) $UnJoinStatus = $ObjMachine.UnjoinDomainOrWorkgroup($Null, $Null) $BSTR = ::SecureStringToBSTR($DomainCred.Password) $Result = $Ping.Send($Record.MachineName) Write-Host "Checking $($Record.MachineName)" -NoNewline $MachineName = $($MachineName.Split("="))Īdd-Member -inputObject $Record -membertype noteProperty ` $MachineParentOU = $($Record.MachinePath).SubString($($MachineName.Length + 1)) $MachineName = $($Record.MachinePath).Split(",") In the end, it worked and for everyone's benefit I have decided to post parts of the resulting script. But, for some reason it seemed to need the machine account to exist in order drop the machine into a workgroup and then back into the domain.Īfter that failure, I turned to a trust old friend called WMI and two methods named: UnjoinDomainOrWorkgroup and JoinDomainOrWorkgroup. Thus leaving the real question, how? NetDom came to mind, and I tried it. Being PowerShell inclined, I knew what I would be using. Naturally, some sort of automation script needed to be employed. How can one remotely make a large number of machines re-join the domain once their accounts have been deleted from the directory? Because the machine accounts where spread across numerous OUs, the sheer numbers delete accounts, and the duration between deletion and realization, doing some type of restore would have proved interesting. Basically, a whole bunch of machine accounts got deleted from a domain.
0 kommentar(er)
