src: http://www.arkf.net/blog/?p=307
For ESXi 5, instead of using esxupdate ( I guess esxupdate is deprecated ), use esxcli :
esxcli software vib install -d /vmfs/volumes/4be1f209-78ae1314-33c5-001b213d3c53/patches/ESXi500-2012813.zip
src: http://www.arkf.net/blog/?p=307
Saturday, June 22, 2013
Wednesday, June 19, 2013
Change time server source on Windows Server 2003 - ntp server
Try a different external time source. You also dont need to stop and start the service anymore in 2003.
Do this:
net time /setsntp:time.nist.gov
w32tm /config /update
w32tm /resync /rediscover /nowait
Check the logs for w32time errors and post back if you get any.
The only machine (DC, member server, client, whatever) you should do this on is the PDC emulator in the root domain. If you type net time /querysntp on ANY other machine in the forest, it should say it is not configured.
Do this:
net time /setsntp:time.nist.gov
w32tm /config /update
w32tm /resync /rediscover /nowait
Check the logs for w32time errors and post back if you get any.
The only machine (DC, member server, client, whatever) you should do this on is the PDC emulator in the root domain. If you type net time /querysntp on ANY other machine in the forest, it should say it is not configured.
Thursday, May 23, 2013
Unable to access from Network locations after UAC enabled
source: http://support.microsoft.com/kb/937624/en-us
Article ID: 937624 - View products that this article applies to.
SYMPTOMS
After you turn on User Account Control in Windows Vista or in Windows 7, programs may be unable to access some network locations. This problem may also occur when you use the command prompt to access a network location.
Note To turn on User Account Control, you click Allow in a User Account Control dialog box.
Note To turn on User Account Control, you click Allow in a User Account Control dialog box.
CAUSE
This problem occurs because User Account Control treats members of the Administrators group as standard users.
When a member of the Administrators group logs on to a Windows Vista-based computer or to a Windows 7-based computer that has User Account Control enabled, the user runs as a standard user. Standard users are members of the Users group. If you are a member of the Administrators group and if you want to perform a task that requires a full administrator access token, User Account Control prompts you for approval. For example, you are prompted if you try to edit security policies on the computer. If you click Allow in the User Account Control dialog box, you can then complete the administrative task by using the full administrator access token.
When an administrator logs on to Windows Vista or to Windows 7, the Local Security Authority (LSA) creates two access tokens. If LSA is notified that the user is a member of the Administrators group, LSA creates the second logon that has the administrator rights removed (filtered). This filtered access token is used to start the user’s desktop. Applications can use the full administrator access token if the administrator user clicks Allow in a User Account Control dialog box.
If a user is logged on to Windows Vista or to Windows 7, and if User Account Control is enabled, a program that uses the user’s filtered access token and a program that uses the user’s full administrator access token can run at the same time. Because LSA created the access tokens during two separate logon sessions, the access tokens contain separate logon IDs.
When network shares are mapped, they are linked to the current logon session for the current process access token. This means that, if a user uses the command prompt (Cmd.exe) together with the filtered access token to map a network share, the network share is not mapped for processes that run with the full administrator access token.
When a member of the Administrators group logs on to a Windows Vista-based computer or to a Windows 7-based computer that has User Account Control enabled, the user runs as a standard user. Standard users are members of the Users group. If you are a member of the Administrators group and if you want to perform a task that requires a full administrator access token, User Account Control prompts you for approval. For example, you are prompted if you try to edit security policies on the computer. If you click Allow in the User Account Control dialog box, you can then complete the administrative task by using the full administrator access token.
When an administrator logs on to Windows Vista or to Windows 7, the Local Security Authority (LSA) creates two access tokens. If LSA is notified that the user is a member of the Administrators group, LSA creates the second logon that has the administrator rights removed (filtered). This filtered access token is used to start the user’s desktop. Applications can use the full administrator access token if the administrator user clicks Allow in a User Account Control dialog box.
If a user is logged on to Windows Vista or to Windows 7, and if User Account Control is enabled, a program that uses the user’s filtered access token and a program that uses the user’s full administrator access token can run at the same time. Because LSA created the access tokens during two separate logon sessions, the access tokens contain separate logon IDs.
When network shares are mapped, they are linked to the current logon session for the current process access token. This means that, if a user uses the command prompt (Cmd.exe) together with the filtered access token to map a network share, the network share is not mapped for processes that run with the full administrator access token.
WORKAROUND
Important This workaround may make your system unsafe. Microsoft does not support this workaround. Use this workaround at your own risk.
To work around this problem, configure the EnableLinkedConnections registry value. This value enables Windows Vista or Windows 7 to share network connections between the filtered access token and the full administrator access token for a member of the Administrators group. After you configure this registry value, LSA checks whether there is another access token that is associated with the current user session if a network resource is mapped to an access token. If LSA determines that there is a linked access token, it adds the network share to the linked location.
To configure the EnableLinkedConnections registry value, follow these steps:
To work around this problem, configure the EnableLinkedConnections registry value. This value enables Windows Vista or Windows 7 to share network connections between the filtered access token and the full administrator access token for a member of the Administrators group. After you configure this registry value, LSA checks whether there is another access token that is associated with the current user session if a network resource is mapped to an access token. If LSA determines that there is a linked access token, it adds the network share to the linked location.
To configure the EnableLinkedConnections registry value, follow these steps:
- Click Start, type regedit in the Start Search box, and then press Enter.
- Locate and then right-click the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
- Point to New, and then click DWORD Value.
- Type EnableLinkedConnections, and then press Enter.
- Right-click EnableLinkedConnections, and then click Modify.
- In the Value data box, type 1, and then click OK.
- Exit Registry Editor, and then restart the computer.
Saturday, May 18, 2013
Nook Tablet rooting and installing cm10 Android
Forget about rooting and looking for obscure filers with vers 47 in them - i did that already...
Here is all you need to install cm10 on our nook tablet...
Thanks to livramax
Installing CM 10 Internally on Nook Tablet
I've been running CM10 build by XDA Developer Succulent version 12/08
on SD card since its release ten days ago, and its reliable/stable
performance has crossed the threshold for me to finally take the plunge
and install it internally on emmc.
FWIW, here the process I used to install CM10 internally on my 16GB Nook Tablet (i.e., on its emmc) (caveat emptor: adopt/follow it at your own risk).
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but not their settings will not be auto-restored) A few additional points worth noting:
Last edited by livramax; 05-11-2013 at 11:54 AM. |
|
![]() |
![]() |
Friday, May 17, 2013
Thursday, May 16, 2013
disable autoRun in XP
Open the registry editor and navigate to the key:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer.
Create a DWORD (32-bit) value named NoDriveTypeAutoRun. If it doesn't already exist.
Right-click the new value and click Modify. Set the hexadecimal value to 000000FF (the decimal equivalent of 255). Now, you can type all the preceding zeros, but you don't need to. You can just enter FF.
source: http://www.techrepublic.com/blog/itdojo/disable-autorun-on-windows-xp-and-vista-with-a-quick-registry-hack/1010
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer.
Create a DWORD (32-bit) value named NoDriveTypeAutoRun. If it doesn't already exist.
Right-click the new value and click Modify. Set the hexadecimal value to 000000FF (the decimal equivalent of 255). Now, you can type all the preceding zeros, but you don't need to. You can just enter FF.
source: http://www.techrepublic.com/blog/itdojo/disable-autorun-on-windows-xp-and-vista-with-a-quick-registry-hack/1010
Wednesday, May 15, 2013
Setting up Launchy to access your Firefox favorites
Store the exported favorites html file in here:
Currently Launchy 2.0 will only search %APPDATA%/Mozilla/Firefox/... for bookmarks.html, so a workaround would be to make a link or copy your FF bookmarks.html there.
Note: Do you work with different Firefox profiles? Please check C:\Documents and Settings\[User name]\Application Data\Mozilla\Firefox\profiles.ini. I think that Weby takes the first line containing "Path=" and extracts the path where to look for the bookmarks.html file. Verify that this first entry points to the Firefox profile you use and, as advised by begesf, if it contains the bookmarks.html with the links you expect. Also note that, at least under WinXP, Firefox may only (re-)export the bookmarks.html file when closing the application.
Currently Launchy 2.0 will only search %APPDATA%/Mozilla/Firefox/... for bookmarks.html, so a workaround would be to make a link or copy your FF bookmarks.html there.
Note: Do you work with different Firefox profiles? Please check C:\Documents and Settings\[User name]\Application Data\Mozilla\Firefox\profiles.ini. I think that Weby takes the first line containing "Path=" and extracts the path where to look for the bookmarks.html file. Verify that this first entry points to the Firefox profile you use and, as advised by begesf, if it contains the bookmarks.html with the links you expect. Also note that, at least under WinXP, Firefox may only (re-)export the bookmarks.html file when closing the application.
Subscribe to:
Posts (Atom)