DHCP / DNS Cleanup, Delete. VMware View


<!-- /* font definitions */ @font-face {font-family:tahoma; panose-1:2 11 6 4 3 5 4 4 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:1627421319 -2147483648 8 0 66047 0;} /* style definitions */ p.msonormal, li.msonormal, div.msonormal {mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"times new roman"; mso-fareast-font-family:"times new roman";} @page section1 {size:595.3pt 841.9pt; margin:70.85pt 70.85pt 2.0cm 70.85pt; mso-header-margin:35.4pt; mso-footer-margin:35.4pt; mso-paper-source:0;} div.section1 {page:section1;} -->

i / have problem...
vmware view, vdi solution (virtual desktops).  solution wonderful, there few little problems.
here a
description of problem;
1. "view" setups machines in (esx) vmware automatic (after settings done, in view administrator).
2. machine names -for example- "office" plus number (pers-1 pers-#### (pers = personnel)).
3. number machine can big... because, there way make sure v-machine (virtual desktop) same before, when use roaming profiles, , central storage home folder. machine "reseted" original settings every logoff.
 -- or machine deleted , made new --automatic-- vmware view "composer" (the admin software).
4. makes new machine new hardware address , new ssid in ads.
5. machine gets ip address dhcp server.
6. works  ----so long---- until dhcp full is... , can take day or two, depending on, use of machines.
7. need able use script (vbs, wmi or c) cleanup dhcp scopes, deleted machine names, or in deletion process, when machine being deleted ads, “deletion process” removes name dhcp , dns/wins (this should automatic; in add/delete process of view system, not!... when machine removed vmware provisioning, should possible use script delete machine name following servers;
dhcp
dns
wins
8. removal of machine name in ads automatic, not know why removal of dhcp name/ip not?
9. major problem, when same naming scheme being used, example:
     --- pers-1 through 25, , 1-25. each time machine used, machine deleted ads, machine names thing remains same... because "new" machine has new hardware address, , ssid. 
ads not having problem, because machines being added, , removed successfully. not dhcp/dns/wins.
result of problem after few uses of “same name” solution, (the machine names "rotate" 1 25, , start 1 again).
dhcp shows same names, more once...
after happens, machine name no longer ping-able/usable.
cth berlin

duplicate thread.
sainath windows driver development.


Windows Server  >  Windows Server General Forum



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group