Phoenix-IT

Member
  • Content count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Phoenix-IT

  • Birthday 11/23/1973

Contact Methods

  • Website URL
    http://

Profile Information

  • OS
    Windows 7 x64
  1. Yay! Thank you, and it was updated yesterday.
  2. Thanks, but it's still grabbing my OS version and automatically grabbing the Windows 7 64 bit version. I guess I'm going to have to build an XP system for the sole purpose of downloading the correct version of Silverlight for my deployment. And THAT, is absolutely ridiculous.
  3. Every option you could want is covered in their Administration Guide: http://forums.adobe.com/servlet/JiveServlet/downloadBody/3063-102-1-3598/flash_player_11_6_admin_guide.pdf Search for "Adobe Flash Extract" to learn how to pull out the MSI packages, etc. from their Administrator's download. Sign up and they'll usually give you a site license to use it in about 5 minutes.
  4. Can someone point me to Microsoft's download of Silverlight for Systems Administrators? I've been searching like mad and can only seem to find it on 3rd party sites, which means it may not be the latest version. When I go to the website specified in the Silverlight Deployment Guide there is no link for administrators or an enterprise version. It checks my system, see's that it's installed, and then refuses to give me a download link. If I disable the plugin, it automatically starts the 64 bit download, when what I need is the 32 bit version for XP SP2 & 3. Makes me wonder what exactly is going on over there at MS, that finding something so basic has become so difficult. Thanks for your help...
  5. Hi Ladies and Gents... I'm having a couple of little issues with WDS on Server 2008 R2 Standard. The WDS Server is not connected to our main network, nor is it connected to the internet. I've set it up specifically for imaging groups of computers for our Desktop Support team. It's connected to a single switch that the clients connect to with no routing or anything like that going on. It's setup with AD, DNS and DCHP, all of which were left to the default setting when I added those roles before adding the WDS role. Almost everything is working fine. I've created boot and capture images, added drivers when necessary and I'm able to capture and re-deploy operating systems as expected. However, I have noticed when I boot more than one machine at a time, while the boot.wim is being transmitted to the machines, two of them can have the same IP address. Most of the time they seem to boot normally, but I do occasionally get an error that the setup program encountered a network error. Is this normal? Second, how many clients need to be imaging at the same time before multicasting will show significant advantage over the normal deployment option? Our desktop guys will probably be imaging anywhere from 5 to 20 machines at a time through a 10/100 or gigabit switch. (Some of the obscure notebooks don't like the gigabit switch.) The reason I ask is because I haven't been able to get multicasting working. I did set it up by-the-book according to Microsoft's WDS getting started guide, but the clients don't ever see the the multicast once they've booted. The only option they show is the normal disk loading process. If multicasting won't make a significant difference when imaging 20 computers on a single switch then it's hardly worth being concerned about. Thanks Much!
  6. I perform centralized desktop management for a large government organization where there are a lot of disparate Domains and Workgroups. I am writing a VBScript that needs to know if a computer is in A domain. Since I may not know of all the domains involved, I can't do a compare-to-known domains and that guarantee a factual result. Knowing how to find out if a user or group account is in a domain already. And that it is relatively simple, as shown below... Dim oGroup, oParent, sResult Set oGroup = GetObject("WinNT://<groupname>,group") Set oParent = GetObject(oGroup.Parent) sResult = oParent.Class ' The returned string determines the source of the user or group. ' "Domain" = A Windows Domain ' "Computer" = A Windows XP/2003/Vista computer. ' "User" = A 2000/NT Computer (odd, but true). I thought that this would work exactly the same for a computer.... Dim oComputer, oParent, sResult Set oComputer = GetObject("WinNT://<computername>") Set oParent = GetObject(oComputer.Parent) ' This will be an IADs Domain Object. sResult = oParent.Class ' oParent.Name would return a string with a Domain or Workgroup name. ' So, sResult SHOULD contain a class string of Domain or Workgroup. ' But sResult will contain "Domain" regardless of whether or not the ' IADs.Domain object contains a Domain or a Workgroup. Since this didn't work, I browsed the IADs Class Library and found a method in the IADs.Domain object called "boolean IsWorkgroup()". Thinking I had found the solution I called the method bResult = oParent.IsWorkgroup() and received a runtime error "Not Implemented". I checked MSDN and the description for this method is "No Longer Implemented". So I am back to square one... So far the only thing that even comes close to what I am looking for is to query WMI - Win32_ComputerSystem and get the "DomainRole". Results for that can include "Standalone Workstation" and "Standalone Server". However, will this information be as reliable/up-to-date as something I can get from ADSI? Any ideas? Thanks...
  7. I've been at this for hours, Google-ing till my head is ready to explode. Maybe someone here has done this. Back around 2000 I had set up a small office network for someone. In the process they asked me to set it up so users could login to any one of their Windows 2000 computers. Since there was no domain controller, I just added the users from one computers ACL to the Administrators group of the other computers (there were only 3). This worked fine, and I haven't run into a similar situation since then because I work in the Enterprise most of the time. My job has recently required some heavy VBScript authoring. I have a stand alone development workstation that I use to test scripts that is running Windows XP Professional SP2. On this workstation I have a stand alone test server running Windows Server 2003 Standard in a virtual machine. The two machines are connected via the Microsoft Loopback adapter with static IP addresses on both sides. The firewall is disabled for this connection and both sides are running the Microsoft Client and File & Printer Sharing. I can browse the network from each machine and see the other, and login and access each other's administrative shares. The problem: I am trying to setup a relationship with these two like I did the old Windows 2000 machines. I want to add my user account on the XP machine to the Administrators group of the Server 2003 virtual machine. When I am in the user manager of the Server, and I type \\<xpmachinename>\<myaccount> to add, it says that it cannot find the object. I have also tried <xpmachine>\<myaccount> and even logging in to the XP's administrative share before trying this. Note that the XP machine doesn't populate in the "Locations" tree either. I have tried playing around with the local security policy and changing some settings related to anonymous logins and that didn't seem to help. Has anyone been successful in adding users and groups from one stand alone workstation or server to another? Would you mind enlightening me? Thanks...
  8. That's what I was wondering... Since WMI is accessable from the network, why can't the script/app run on the server and configure the client remotely? The thing is, I'd have no idea how to go about that. Thanks for all your replies folks... You were a big help.
  9. Greetings! Been reading these forums for a while, but this is my first posting. I'm getting a little overwhelmed at work by projects that involve a lot of administration tasks. I'm looking to automate and am trying to decide which language is best to learn; VB.Net or VBScript. I understand that VBScript is on it's way out. However, does VB.Net support all of the WMI & ASDI functionality that VBScript does? Thanks Much!