Yeah seen the Fed Ex's already have those blackholed, I guess USPS was
on the list also. Had a few users that fell for the attack therefore had
to do a little bit of Incident Response yesterday (FUN FUN!)
Ran across another cool blog from Larry Zelster about PDF malware
analysis, that is very
Hey all,
I have a client who is using 2 ISA 2006 servers in an array. ISA 1 is for the
internal clients with a subnet of 192.168.0.0 and ISA 2 is the external access
with a WAN IP and DMZ. The WAN IP is bound to the NIC along with a block of
secondary IP's. They use a web application that,
For all our employees, we have general purpose accounts added to our Outlook
profile and it doesn't cause any issues.
It doesn't 'sync' them per se, and it doesn't even seem to query the folder
data until that folder is actually 'clicked' on, or viewed, in Outlook.
Therefore alleviating any
Or even the more simpler: 'Open other folder' option. This way doesn't add
them to your folder list.
This doc highlights both methods quite nicely:
http://kb.iu.edu/data/agny.html
I'd still recommend my first method if the mailboxes are accessed
frequently.
Sam
From: Sam Cayze
Other than not requiring a hardware contract, they pretty much behave the
same, with the same management needs.
In order to keep VM sprawl down, it's sometimes necessary to implement
stricter commissioning procedures for new servers and workstations, and/or
restrict admin rights. I'm assuming
Since they are not servers per se, I just label them appropriately via
prefixing the computer name by 'VM-' (Since all my physical computers name
are the serial numbers).
If I had a lot, I'd probably dump them in their own OU.
Other than that, they get all the same GPs and WSUS settings as
Our hardware machines are identified by their property tag # our VMs are
named after characters in Lord of the Rings.
-
Who'd you rather be, the Beatles or the Rolling Stones?
On Wed, Jun 1, 2011 at 09:16, Sam Cayze sca...@gmail.com wrote:
Since they are not servers per se,
OK. I have a Win2008 AD in a parent/child configuration. I am trying to
set up a testing version of it, using VMware. (I have a VM DC of both
the parent and child domains). We want a lab version of our domain, to
test proposed changes to OUs, GPOs, etc.
So I cloned both DCs, and set them on a
I've done ours; schema is 2008 R2 + Exchange 2010 but all the DCs are 2003.
No issues at this stage.
--
Sent using BlackBerry
From: Senter, John [mailto:john.sen...@etrade.com]
Sent: Wednesday, June 01, 2011 01:02 PM
To: NT System Admin Issues
OK. I just found out that I have this error in my production domain.
(so at least that means I didn't screw up my cleanup). I did a DCDIAG
/C /V on the production parent DC, and got the same error). We use DFS
replication now (I'm told); perhaps that's why this test fails?
SO:
parent DC: says
On 6/1/2011 12:05 PM, David Lum wrote:
Do you guys treat VM’s any differently than a physical machine? In my
environment we are starting to get several of our Mac developers having
WinOS VM’s running on them.
No. In fact, I have 2 DCs that are VMs in VMware ESX 4.1.
~ Finally, powerful
Sounds like you just have some extra NTFRS or DFS replication objects that have
been missed--take a look at http://support.microsoft.com/kb/216498.
-Bonnie
-Original Message-
From: Mike Leone [mailto:oozerd...@gmail.com]
Sent: Wednesday, June 01, 2011 9:57 AM
To: NT System Admin Issues
I'm having trouble importing a VM created and exported on a machine running
2008R2 to a machine running 2008. Do I need to upgrade Hyper-V manager on
the 2008 machine or something? Of course this is a matter of utmost urgency.
James
~ Finally, powerful endpoint security that ISN'T a resource
On 6/1/2011 1:11 PM, Miller Bonnie L. wrote:
Sounds like you just have some extra NTFRS or DFS replication objects that
have been missed--take a look at http://support.microsoft.com/kb/216498.
-Bonnie
Well, I'm seeing this error in my production domain, too (see my later
message). So this
We have a few hundred in virtual environments. We do not name them
differently and treat them the same pretty muh.
On Wed, Jun 1, 2011 at 10:08 AM, Mike Leone oozerd...@gmail.com wrote:
On 6/1/2011 12:05 PM, David Lum wrote:
Do you guys treat VM’s any differently than a physical machine? In
No, we treat VMs very similarly to physical systems for the most part...
About 20% of our production environment and 50% of our development
environment is virtual.
*ASB *(Professional Bio http://about.me/Andrew.S.Baker/bio)
*Harnessing the Advantages of Technology for the SMB market...
*
I can't find anything about this with Google. If needed, can I do a standing
upgrade of a production server from Windows 2008 to R2 without causing a
bunch of issues, I could always do that this evening after hours.
On Wed, Jun 1, 2011 at 1:41 PM, James Kerr cluster...@gmail.com wrote:
I'm
I hadn't seen your second reply before sending, but have you ever removed a DC
from your production domain? You might have a lingering object somewhere.
-Original Message-
From: Mike Leone [mailto:oozerd...@gmail.com]
Sent: Wednesday, June 01, 2011 10:44 AM
To: NT System Admin Issues
On 6/1/2011 2:11 PM, Miller Bonnie L. wrote:
I hadn't seen your second reply before sending, but have you ever removed a
DC from your production domain? You might have a lingering object somewhere.
We've removed DCs before, sure. But they've all been graceful removals,
with DCPROMO. (for
We're about 80% virtual.
On Wed, Jun 1, 2011 at 11:12 AM, Andrew S. Baker asbz...@gmail.com wrote:
No, we treat VMs very similarly to physical systems for the most part...
About 20% of our production environment and 50% of our development
environment is virtual.
*ASB *(Professional Bio
Got it! We were using an old version of DCDIAG (dated 2007-02-17, file
version 5.2.3790.3959), that I guess was installed from a Win2003
Support Tools pack. When I run the DCDIAG dated 2010-11-20, file version
6.1.7601.17514, in the \WINDOWS\SYSTEM32 folder, everything works and
all tests pass.
Whew--glad it's all working for you!
-Original Message-
From: Mike Leone [mailto:oozerd...@gmail.com]
Sent: Wednesday, June 01, 2011 12:05 PM
To: NT System Admin Issues
Subject: Re: DC fails VerifyReferences after cleaning up removed DCs -
Q312862 - SOLVED
Got it! We were using an old
We're about 95% virtualized here. The only things that aren't virtual,
really, are our SQL boxes.
Andrew S. Baker asbz...@gmail.com 6/1/2011 11:12 AM
No, we treat VMs very similarly to physical systems for the most
part...
About 20% of our production environment and 50% of our development
On 6/1/2011 3:35 PM, Joseph Heaton wrote:
We're about 95% virtualized here. The only things that aren't virtual,
really, are our SQL boxes.
Yeah, we rarely, if ever, run SQL on virtual boxes. Except for really
small DBs, maybe. And certainly not the larger production DBs, which are
up around
We run a production MS SQL DB at just over 300gb on a VM just fine. The key is
making sure that you have the proper hardware.
We've ran this for over a year just fine.
-Original Message-
From: Mike Leone [mailto:oozerd...@gmail.com]
Sent: Wednesday, June 01, 2011 2:43 PM
To: NT System
*If needed, can I do a standing upgrade of a production server from
Windows 2008 to R2 without causing a bunch of issues, I could always do that
this evening after hours.*
2008 R2 is 64-bit only. If your 2008 instance is 64-bit, then the answer is
yes. I've done it a half-dozen times or so.
We are about 60-70% Virtual, and heading towards a goal of 90% + Virtual
in the near future.
Z
Edward E. Ziots
CISSP, Network +, Security +
Security Engineer
Lifespan Organization
Email:ezi...@lifespan.org
Cell:401-639-3505
From: Andrew S. Baker [mailto:asbz...@gmail.com]
Sent:
We're virtually all virtual, and our VMs are managed the same as the few
physical Windows server we have.
From: Ziots, Edward [mailto:ezi...@lifespan.org]
Sent: Wednesday, June 01, 2011 3:27 PM
To: NT System Admin Issues
Subject: RE: VM's in AD
We are about 60-70% Virtual, and heading towards a
I need to change the static IP of a couple of my DCs (which of course
are DNS servers, too). Searching around, it seems that I should just be
able to change the static IP address the same way you change any Windows
static IP.
Yet when I do that, my DNS breaks. dnslint reports No matching CNAME
You will want to do at least the following:
- Create new A records for the DCs using the new IPs
- Create new reverse entries for the DCs
- Ensure that your DNS service is listening on the new IP
I usually change the IP address on each box, making the old IP the secondary
IP, then
Umm... when you say I should just be able to change the static IP address
the same way you change any Windows
static IP are you meaning going into the NIC properties and changing them
there? What about the DNS records, I'm no expert, but wouldn't you want to
update those as well or is that what
You don't need to do either of the first two. Worst case just bounce the box
when you're done.
Thanks,
Brian Desmond
br...@briandesmond.commailto:br...@briandesmond.com
c - 312.731.3132
From: Andrew S. Baker [mailto:asbz...@gmail.com]
Sent: Wednesday, June 01, 2011 3:59 PM
To: NT System
Dynamic registration will take care of this.
Thanks,
Brian Desmond
br...@briandesmond.com
c - 312.731.3132
-Original Message-
From: John Aldrich [mailto:jaldr...@blueridgecarpet.com]
Sent: Wednesday, June 01, 2011 4:13 PM
To: NT System Admin Issues
Subject: RE: How to change IP
On 6/1/2011 5:12 PM, John Aldrich wrote:
Umm... when you say I should just be able to change the static IP address
the same way you change any Windows
static IP are you meaning going into the NIC properties and changing them
there?
Correct.
On 6/1/2011 5:22 PM, Brian Desmond wrote:
*You don’t need to do either of the first two. Worst case just bounce
the box when you’re done.*
So .. just change the IP address in the NIC properties of this DC
(including changing the DNS server settings to point to the new IP
address you are using
That's what I would do. Obviously you'll need to repoint clients using the
machine for DNS, etc.
Thanks,
Brian Desmond
br...@briandesmond.com
c - 312.731.3132
-Original Message-
From: Mike Leone [mailto:oozerd...@gmail.com]
Sent: Wednesday, June 01, 2011 5:12 PM
To: NT System
On 6/1/2011 6:16 PM, Brian Desmond wrote:
That's what I would do. Obviously you'll need to repoint clients using the
machine for DNS, etc.
HUH. OK ... haven't set up any clients yet. Changing the IP address (so
it's a different subnet from production, even tho already isolated, is
the last
Have you tried simply creating a new VM using the VHD('s) that came from the
R2 server (instead of importing)?
At the very least, a little googling suggests that the integration services
(from R2) should removed and then re-installed from the non-R2 server. But
if the hardware is available,
38 matches
Mail list logo
